>>> On Wed, Jun 6, 2007 at 11:40 AM, in message <[EMAIL PROTECTED]>, "McKown, John" <[EMAIL PROTECTED]> wrote: -snip- > And I doubt that you can use gdb to look at it. And it dumps the entire > image, not just the current process.
There's a tool to convert CP dumps to lcrash format, so that's not a big issue. Having far more to wade through than necessary would be more of a problem. But, your comment about gdb got me to thinking. You can invoke gdb by telling it to attach itself to a running process. You can also give it a text file containing commands to run after it's invoked. Put the two together, and a running program _might_ be able to figure out its own PID, write some commands out to a temp file, invoke gdb, and keep on running. Implementation is left as an exercise for the reader, since I don't code in C/C++. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
