Re: collecting "oobs" message for user applications (WAS: Re: stack trace without core)

On Jun 22, 8:58 pm, RezaRob <Reza...@xxxxxxxxx> wrote:

Sorry I didn't clarify this: It's okay for the main process to be
killed; however, it's core may be gigabytes huge, and I only want a
small "stack trace."

Did you read the part about using __builtin_return_address and dladdr?

Really, I want some kind of "oobs!" message, like the one the kernel
dumps. I guess a signal handler can just copy the stack into a "core"
file, but then, how do you prevent gdb from complaining "this is not a
core file?"

Can you ship an executable with symbols that's dynamically linked? In
that case, just call 'dladdr'.

DS

.

Relevant Pages

  • Re: Scheme Virtual Machine
    ... Minimal c/c++ made core for the executable file everything else in the ... I had a similar idea in mind when writing my Implementation of scheme ... The VM uses a stack to pass arguments. ... executes an if operation with a 'then' and an 'else' branch. ...
    (comp.lang.scheme)
  • RE: Weird one
    ... Solaris isn't Linux and there are a lot of potential differences under the ... There are a couple of ways that you can write and control the stack, ... On a multi-core /smp Linux box, does each CPU have its own stack or does ... Meaning if Thread A from the same process is on core 1, ...
    (comp.databases.informix)
  • Re: Debugging core in different environment
    ... Suppose the core is generated in the production environment. ... Is it feasible to debug that core in development environment ... otherwise you need to follow following tricks and need to build stack ...
    (comp.unix.programmer)
  • collecting "oobs" message for user applications (WAS: Re: stack trace without core)
    ... event of an exception I need a stack trace. ... The simplest solution is to 'fork' and have the child call 'abort' to ... generate a core dump. ... own stack dump routine if the stack dump routine faults!) ...
    (comp.os.linux.development.apps)
  • Re: collecting "oobs" message for user applications (WAS: Re: stack trace without core)
    ... dumps. ... I guess a signal handler can just copy the stack into a "core" ... If I just dump the stack, is there any way to tell gdb to reconstruct ...
    (comp.os.linux.development.apps)