Nmap Development mailing list archives

Getting a stack trace


From: Ron <ron () skullsecurity net>
Date: Mon, 15 Dec 2008 20:32:44 -0600

Hi all,

I've brought this up before, but I'm not sure if anything ever happened
with it and it's pretty important.

Could the script engine be changed to display a stacktrace when an error
happens (only if debug mode is enabled would be good)?

Me and Brandon are trying to debug an error that shows up in
stdnse.print_debug(), but, because print_debug() is called from just
about every function in my code, it's incredibly difficult to trace it
back. I've run into this issue before, too, but normally I can trace it
back by looking at the code I'd just written, but when it shows up later
in testing that isn't feasable.

So yeah, any chance of somebody writing that?

Thanks,
Ron

-- 
Ron Bowes
http://www.skullsecurity.org/

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


Current thread: