From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix frame-issue with watchpoints...
Date: Fri, 06 Oct 2006 17:34:00 -0000 [thread overview]
Message-ID: <20061006173348.GC980@adacore.com> (raw)
In-Reply-To: <20061006020348.GB980@adacore.com>
> > > One way to bandaid this, probably along the lines that Andrew was
> > > trying to do (try to recover from a situation that should not happen),
> > > is to replace "current_frame" by get_current_frame().
> >
> > Or just kill it.
>
> Let me do a testsuite run without this code, and see what comes out
> of it. Perhaps it's time to kill it.
Hum, unfortunately we had one testcase where the assertion failed:
-var-create a2 0xbffff6b8 a^M
~"frame.c:1238: internal-error: get_prev_frame: Assertion `this_frame != NULL' failed.\nA problem internal to GDB has been detected,\nfurther debugging may prove unreliable.\nQuit this debugging session? "^M
~"(y or n) "^M
ERROR: Got interactive prompt.
UNRESOLVED: gdb.mi/mi-var-display.exp: create variable a2 in different scope
--
Joel
prev parent reply other threads:[~2006-10-06 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 0:50 Joel Brobecker
2006-10-06 1:20 ` Daniel Jacobowitz
2006-10-06 2:03 ` Joel Brobecker
2006-10-06 17:34 ` Joel Brobecker [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=20061006173348.GC980@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@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