From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite/c++] test script for PR c++/186
Date: Sun, 23 Nov 2003 22:08:00 -0000 [thread overview]
Message-ID: <20031123220827.GA18290@nevyn.them.org> (raw)
In-Reply-To: <20031123220445.1F77C4B409@berman.michael-chastain.com>
On Sun, Nov 23, 2003 at 05:04:45PM -0500, Michael Chastain wrote:
> -re "= {.*a1 = 100.*b1 = .*b2 = .*}\r\n$gdb_prompt $" {
> # gcc 2.95.3 -gstabs+
> # gcc 3.3.2 -gdwarf-2
> # gcc 3.3.2 -gstabs+
> # Someone might argue that gdb is not buggy here but I think it is.
> kfail "gdb/186" "print * beta_p at marker close brace #1"
> }
Then what are you proposing we do? The variable has been destroyed.
Its value isn't required to be there any more. If we had enough scope
information to print an error, maybe we could do that. But I don't
think we do.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-11-23 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-23 22:05 Michael Elizabeth Chastain
2003-11-23 22:08 ` Daniel Jacobowitz [this message]
2003-11-23 22:22 ` Daniel Jacobowitz
2003-11-24 17:23 ` David Carlton
2003-11-23 23:00 Michael Elizabeth Chastain
2003-11-24 17:25 ` David Carlton
2003-11-24 16:41 Michael Elizabeth Chastain
2003-11-24 17:27 ` David Carlton
2003-11-24 18:13 Michael Elizabeth Chastain
2003-11-24 20:02 ` David Carlton
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=20031123220827.GA18290@nevyn.them.org \
--to=drow@mvista.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