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

On Jun 23, 6:05 pm, David Schwartz <dav...@xxxxxxxxxxxxx> wrote:
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?

Actually, not carefully. Sorry.


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'.

I would prefer not to do that. I wonder, is that how mozilla does
that "do you want to send crash info" thing?

If I just dump the stack, is there any way to tell gdb to reconstruct
the thing after the fact? For instance, can gcc generate a separate
file similar to the "system.map" file that the kernel uses?

I really appreciate your suggestions and help :-)

Reza.

.

Relevant Pages