From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: Pending breakpoints and scripts
Date: Tue, 10 Feb 2004 22:26:00 -0000 [thread overview]
Message-ID: <20040210222616.GA32636@nevyn.them.org> (raw)
In-Reply-To: <40294BA1.3020906@gnu.org>
On Tue, Feb 10, 2004 at 04:22:41PM -0500, Andrew Cagney wrote:
> >On Mon, Feb 09, 2004 at 03:02:19PM -0500, Andrew Cagney wrote:
> >
> >>Anyone noticed this?
> >>
> >>(top-gdb) run testsuite/gdb.base/advance
> >>Starting program: ...
> >>Setting up the environment for debugging gdb.
> >>Function "internal_error" not defined.
> >>Breakpoint 1 (internal_error) pending.
> >>Function "info_command" not defined.
> >>Breakpoint 2 (info_command) pending.
> >>(top-gdb)
> >>
> >>It's caused by this:
> >>
> >> if (!query ("Make breakpoint pending on future shared library
> >>load? ")
> >>)
> >> return rc;
> >>
> >>The old behavior was: when in batch mode, throw an error (and hence
> >>abandon the script) if the breakpoint insert fails.
> >>
> >>The new behavior is: when in batch mode, always insert the breakpoint.
> >>when not in batch mode never throw an error.
> >>
> >>For the existing behavior to be restored the query's logic would need to
> >>be reversed (ask the oposite question) and then re-throw the error. A
> >>/pending qualifier could then be added.
> >>
> >>Thoughts?
> >
> >
> >I'd rather not reverse the question. We could check from_tty at the
> >call site, and not set pending breakpoints if no tty...
>
> Why?
Well, how would you word it? It makes more intuitive sense to me to
answer 'y' to create something special and 'n' to do nothing, than the
other way around.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-10 22:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 20:02 Andrew Cagney
2004-02-09 22:32 ` Daniel Jacobowitz
2004-02-10 21:22 ` Andrew Cagney
2004-02-10 22:26 ` Daniel Jacobowitz [this message]
2004-02-11 3:48 ` System calls debugging MuthuKumar-Hotpop
2004-02-12 9:58 ` how to include subdirectories too, for the source directory murugesan
2004-02-12 13:07 ` Bob Rossi
2004-02-13 4:23 ` murugesan
2004-02-11 14:31 ` Pending breakpoints and scripts Andrew Cagney
2004-02-11 14:47 ` Daniel Jacobowitz
2004-02-17 19:24 ` Andrew Cagney
2004-02-17 19:31 ` Daniel Jacobowitz
2004-02-17 19:39 ` Andrew Cagney
2004-02-17 19:41 ` Daniel Jacobowitz
2004-02-17 20:07 ` Jeff Johnston
2004-02-17 20:14 ` Andrew Cagney
2004-02-17 20:15 ` Daniel Jacobowitz
2004-02-17 20:13 ` Andrew Cagney
2004-02-17 20:15 ` Daniel Jacobowitz
2004-02-17 20:30 ` Andrew Cagney
2004-02-17 20:35 ` Daniel Jacobowitz
2004-02-19 22:42 ` [RFA]: Patch for pending " Jeff Johnston
2004-02-23 15:56 ` Andrew Cagney
2004-02-09 22:27 Pending " Michael Elizabeth Chastain
2004-02-09 22:38 ` Andrew Cagney
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=20040210222616.GA32636@nevyn.them.org \
--to=drow@mvista.com \
--cc=cagney@gnu.org \
--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