From: Andrew Cagney <ac131313@ges.redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: jason-swarelist@molenda.com, gdb@sources.redhat.com
Subject: Re: RFC gdb crashes on watchpoint that's no longer valid
Date: Wed, 14 Aug 2002 21:26:00 -0000 [thread overview]
Message-ID: <3D5B2D5D.5060102@ges.redhat.com> (raw)
In-Reply-To: <7263-Wed14Aug2002140112+0300-eliz@is.elta.co.il>
>> Date: Tue, 13 Aug 2002 15:21:24 -0700
>> From: Jason Molenda <jason-swarelist@molenda.com>
>>
>> Do either of these approaches appeal to anyone?
>
>
> My vote is for removing the watchpoint, but I think the message
> should be more clear. For example:
>
> if (! gdb_parse_exp_1 (&s, innermost_block, 0, &(b->exp)))
> {
> warning ("Unable to reset watchpoint %d (some of "
> "its variables don't exist); deleting", b->number);
Mine is for: do the same as for breakpoints (unless that is also
dump-core :-)
Andrew
prev parent reply other threads:[~2002-08-15 4:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 15:21 Jason Molenda
2002-08-13 15:55 ` Jason Molenda
2002-08-14 4:03 ` Eli Zaretskii
2002-08-14 21:26 ` Andrew Cagney [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=3D5B2D5D.5060102@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=jason-swarelist@molenda.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