From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Watchpoint segfaults
Date: Sat, 10 Dec 2005 15:57:00 -0000 [thread overview]
Message-ID: <20051210155740.GA9227@nevyn.them.org> (raw)
In-Reply-To: <uhd9he4l5.fsf@gnu.org>
On Sat, Dec 10, 2005 at 10:31:02AM +0200, Eli Zaretskii wrote:
> > Date: Fri, 9 Dec 2005 14:58:11 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > I think we want to temporarily disable breakpoints whose expression can't be
> > parsed
>
> I agree. But perhaps instead of just disabling it we should display
> some warning the first time we find that we are unable to parse its
> expression.
That sounds like a good idea. We should also try to re-parse it at any
available opportunity, e.g. when the symbol table changes. This'll
take a little work to get right.
> > and print it as a string rather than using the expression printer.
>
> Print it where? in the table displayed by "info breakpoints" or
> equivalent commands? Or do you have some other situation in mind?
Sorry, yes, I was referring to the "info breakpoints" segfault.
Basically someone's going to have to go through and audit the uses of
->exp.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-12-10 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 19:58 Daniel Jacobowitz
2005-12-10 8:31 ` Eli Zaretskii
2005-12-10 15:57 ` Daniel Jacobowitz [this message]
2005-12-10 19:38 ` Eli Zaretskii
2005-12-10 19:58 ` Ramana Radhakrishnan
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=20051210155740.GA9227@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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