From: Keith Seitz <keiths@redhat.com>
To: Thomas Fusco <tfusco@link.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: SEG FAULT
Date: Fri, 21 Jan 2005 23:32:00 -0000 [thread overview]
Message-ID: <1106350346.3653.75.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <41F16D23.3060409@link.com>
On Fri, 2005-01-21 at 12:59, Thomas Fusco wrote:
> I'm getting a "SEGMENTATION FAULT" with the address and I'm having
> trouble getting to the address using insight. I can locate an address
> if I'm in the function browser and I disassemble and hunt for the
> address (using window). But what if I do not know which function I'm
> getting the SEGMENTATION FAULT on. It's tedious to hunt through all the
> code.
I'm afraid you're going to have to give a little more information. Can
you see a stack backtrace? [Open stack window; or open console window
and type "bt".]
You should be able to deduce what happened unless the program did
something that corrupted the stack or whatnot.
If you send the output of "bt", I can tell you the best way to proceed.
[Feel free to obfuscate function names if you're worried about it.]
If you know the address where the segfault occurred, you can open a
console window and type "info symbol ADDRESS" to find out what symbol
best matches the address:
$ ./gdb -nw -nx -q gdb
(gdb) p main
$1 = {int (int, char **)} 0x8090e70 <main>
(gdb) info symbol 0x8090e74
main + 4 in section .text
Keith
prev parent reply other threads:[~2005-01-21 23:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 20:59 Thomas Fusco
2005-01-21 23:32 ` Keith Seitz [this message]
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=1106350346.3653.75.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=tfusco@link.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).