From: Daniel Jacobowitz <drow@false.org>
To: wim delvaux <wim.delvaux@adaptiveplanet.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.1-debian : problem with restarting program with breakpoints on dynamic libraries#
Date: Thu, 03 Jun 2004 20:47:00 -0000 [thread overview]
Message-ID: <20040603204718.GB22683@nevyn.them.org> (raw)
In-Reply-To: <200406031355.19172.wim.delvaux@adaptiveplanet.com>
On Thu, Jun 03, 2004 at 01:55:19PM +0200, wim delvaux wrote:
> As requested a transcript :
>
> ---> Mark the setting of the breakpoint to AP_RaiseExc
> ---> Mark the FAILURE of settting the breakpoint in the second run
That says that it failed to set the breakpoint several times, not that
it never succeeded. Try continuing to the point where the breakpoint
would hit and you should find that the breakpoint was placed. If
that's not the case, please show a transcript and check "info
breakpoints".
The error messages themselves are a long-standing bug.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-06-03 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 22:28 wim delvaux
2004-06-03 3:57 ` Daniel Jacobowitz
2004-06-03 11:55 ` wim delvaux
2004-06-03 20:47 ` Daniel Jacobowitz [this message]
2004-06-03 21:49 ` wim delvaux
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=20040603204718.GB22683@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=wim.delvaux@adaptiveplanet.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