From: David Relson <relson@osagesoftware.com>
To: gdb@sources.redhat.com
Subject: Re: Odd behavior with souce files
Date: Mon, 10 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20011210161846.00cdbcc0@mail.osagesoftware.com> (raw)
In-Reply-To: <8582-Mon10Dec2001211941+0200-eliz@is.elta.co.il>
At 02:19 PM 12/10/01, you wrote:
> > Date: Mon, 10 Dec 2001 13:46:30 -0500 (EST)
> > From: "Kevin R.J. Ellwood" <kellwood@ford.com>
> >
> > (gdb)
> > 2806 in malloc.c
> >
> > Needless to say, I don't want to debug malloc.
Sounds like you're using "step" when you should be using "next" ...
>Does it help to say "finish" whenever you wind up inside a library
>function?
>
> > Is there an option for gdb such that, if a source file is not found,
> > it won't try to step into that particular routine.
>
>GDB does that for me if the library functions have no debug info. You
>could say "strip --strip-debug libc.a", for example. But given the
>"finish" trick, I'd not bother (you could need the library debug info
>some day).
next prev parent reply other threads:[~2001-12-10 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 10:47 Kevin R.J. Ellwood
2001-12-10 11:21 ` Eli Zaretskii
2001-12-10 13:20 ` David Relson [this message]
2001-12-11 0:13 ` 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=4.3.2.7.2.20011210161846.00cdbcc0@mail.osagesoftware.com \
--to=relson@osagesoftware.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