From: Daniel Jacobowitz <drow@false.org>
To: Timo Steuerwald <timo.steuerwald@gmx.de>
Cc: gdb@sources.redhat.com
Subject: Re: _dl_debug_state_internal () breakpoints
Date: Sun, 03 Oct 2004 18:00:00 -0000 [thread overview]
Message-ID: <20041003171529.GA5482@nevyn.them.org> (raw)
In-Reply-To: <415C0145.18615.348D2@localhost>
On Thu, Sep 30, 2004 at 12:51:17PM +0200, Timo Steuerwald wrote:
> Hi all,
>
> I currently debug an application with many of that type of "internal
> breakpoints":
> > #0 0x4000c690 in _dl_debug_state_internal () from /lib/ld-linux.so.2
> This breaks are a little bit annoying :-(
>
> After some searching on the internet, I've found the following thing:
> http://sources.redhat.com/ml/gdb/2003-10/msg00014.html
> So my question is, is it possible to configure gdb in such way, that after hitting
> this breakpoint, the debugged application will be automatically continued? Or
> to disable this breakpoint at all?
GDB should never stop at this breakpoint and give you a prompt. You
need to tell us more about what this application is doing, and
investigate why GDB decided to stop.
--
Daniel Jacobowitz
prev parent reply other threads:[~2004-10-03 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 10:53 Timo Steuerwald
2004-10-03 18:00 ` Daniel Jacobowitz [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=20041003171529.GA5482@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=timo.steuerwald@gmx.de \
/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).