Jump to content




Unable to debug program


  • You cannot reply to this topic
2 replies to this topic

#1 MindenCucc

  • Members
  • 179 posts
  • Location/home/marcus/

Posted 18 June 2015 - 06:56 PM

Hi!

My problem is that I wrote a program that prints out a stacktrace of the running program if something errors, but if the window API errors, the computer just turns off with a "Goodbye" message.

My "debugger":

Spoiler

I can't find the location of the error in the main file, because it's really big.

Edit: is it possible to break out of the derpy window API in the multishell? Because it caused a lot of headaches because of this bug :(

Edited by MindenCucc, 18 June 2015 - 06:59 PM.


#2 Bomb Bloke

    Hobbyist Coder

  • Moderators
  • 7,099 posts
  • LocationTasmania (AU)

Posted 18 June 2015 - 10:57 PM

View PostMindenCucc, on 18 June 2015 - 06:56 PM, said:

Edit: is it possible to break out of the derpy window API in the multishell? Because it caused a lot of headaches because of this bug :(

term.redirect(term.native())


#3 MindenCucc

  • Members
  • 179 posts
  • Location/home/marcus/

Posted 18 June 2015 - 11:48 PM

Oh, okay, thanks :D I totally forgot that :P But since I used wrapped versions of set*Color-s, I just inserted an error-checking snippet, and now it doesn't turn off on term API error :D





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users