From: "Robin Rowe" <rower@MovieEditor.com>
To: <gdb@sources.redhat.com>
Subject: Crash log
Date: Mon, 22 Sep 2003 20:46:00 -0000 [thread overview]
Message-ID: <0ca201c3814a$8e899490$0200a8c0@tbird> (raw)
Hi. This isn't really a gdb question, but I don't know where else to ask.
When a program catches a bad signal such as SIGSEGV I want to write a crash
log entry before the program exits. Is there anything useful I can put in
the log besides the name of the program and when it crashed? Is it ok to
write this log from my signal catcher, or should it first fork?
Is there some kind of useful state info (assuming the program contains no
debugging info) that I can write to a log file at the time of death? Can I
get an instruction pointer that I can relate back to the original souce
somehow to determine what line of code crashed?
Thanks!
Robin
---------------------------------------------------------------------------
Robin.Rowe@MovieEditor.com Hollywood, California
www.CinePaint.org Free motion picture and still image editing software
next reply other threads:[~2003-09-22 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 20:46 Robin Rowe [this message]
2003-09-23 5:03 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='0ca201c3814a$8e899490$0200a8c0@tbird' \
--to=rower@movieeditor.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox