From: Michal Ludvig <mludvig@suse.cz>
To: Terje Eggestad <terje.eggestad@scali.com>
Cc: gdb@sources.redhat.com
Subject: Re: Strange segfaults of gdb
Date: Sat, 14 Dec 2002 06:09:00 -0000 [thread overview]
Message-ID: <3DFB3BAB.8040908@suse.cz> (raw)
In-Reply-To: <1039817373.10496.19.camel@eggis1>
Terje Eggestad wrote:
> One other detail, when you get a seg fault, or just simply break on a
> symbol in libc, like strlen(), (first noticed it b/c a seg fault in
> strlen) neither bt or where give the stack trace... That's a bug, right?
Well, it depends on the point of view :-)
These functions don't have a debug info, because they are pure assembler
functions not written in C (applies to memcpy, str*, and some others, as
well as for syscall wrappers). Without a valid Dwarf2 information GDB
can't do a backtrace. However I don't treat this as a GDB bug, but
anyway I'm implementing a workaround for this, because I know it's
annoying :-)
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz
next prev parent reply other threads:[~2002-12-14 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 16:36 Terje Eggestad
2002-12-13 9:59 ` Michal Ludvig
[not found] ` <1039817373.10496.19.camel@eggis1>
2002-12-14 6:09 ` Michal Ludvig [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 9:12 Michal Ludvig
2002-04-11 14:43 ` Michael Snyder
2002-04-12 2:13 ` Eli Zaretskii
2002-04-12 4:27 ` Michal Ludvig
2002-04-12 5:05 ` Eli Zaretskii
2002-04-16 11:16 ` Michael Snyder
2002-04-17 3:12 ` Michal Ludvig
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=3DFB3BAB.8040908@suse.cz \
--to=mludvig@suse.cz \
--cc=gdb@sources.redhat.com \
--cc=terje.eggestad@scali.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