home ... me ... pictures ... email ... feed ... rust chronicles... twitter...

March 22, 2005

woo stack trace!

I find that I can actually just grab the stack of the program
and index it back up against the binary later to get a stack
trace. Might even be able to run against stripped and
match against symbol-containing. Now I just have to go and
automate all this framework so I can grab the stack at
intervals instead of using a debugger and having all kinds
of crap loaded and being slow.

It needs a name, even though right now it's just a hack with
/proc, memgrep, and some binutils.

music: Beck: E-Pro

candice at March 22, 2005 07:37 PM

Comments

If you haven't checked out google-coredumper yet, you should:

https://sourceforge.net/projects/goog-coredumper/

"The coredumper library can be compiled into applications to create core dumps of the running program, without termination. It supports both single- and multi-threaded core dumps, even if the kernel doesn't natively support for multi-threaded core files."

Although, being able to do it to any arbitrary running process using procfs hackery is kinda cool, too. That is, what I assume you're doing?

Posted by: Dossy at March 22, 2005 09:47 PM

That is what I'm doing yes, procfs hacks. The ornery piece of spaghetti code that prompted its' existence tends to start behaving while being debugged, added to, etc.

That looks like it may be useful (the coredumper).

Posted by: candice at March 22, 2005 09:56 PM

« if i were a rich girl... ... Current ... this is gonna be a series »