From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: "H. J. Lu" <hjl@lucon.org>, Elena Zannoni <ezannoni@redhat.com>,
GDB <gdb@sources.redhat.com>
Subject: Re: RFC: DW_TAG_try_block
Date: Wed, 28 May 2003 16:50:00 -0000 [thread overview]
Message-ID: <20030528165012.GA3644@nevyn.them.org> (raw)
In-Reply-To: <ro13ciz3ton.fsf@jackfruit.Stanford.EDU>
On Wed, May 28, 2003 at 09:46:48AM -0700, David Carlton wrote:
> On Tue, 27 May 2003 08:13:34 -0700, "H. J. Lu" <hjl@lucon.org> said:
>
> > When it is compiled by ecc 7.1,
>
> > # ecc -g main.cc -o main
>
> > The current gdb won't see ni nor n when break points are set in try
> > and catch blocks.
>
> [ Source code deleted, but thanks. ]
>
> I was going to volunteer to add this to the test suite, but it looks
> like something like that is already there: am I correct in thinking
> that gdb.c++/try-catch.exp fails if you're using ecc as your compiler?
> (How do you tell runtest to use a different C compiler, anyways? Does
> "CC=ecc runtest gdb.c++/try-catch.exp" work?)
No; I have to create a custom board file and use "set board_info
c++compiler ecc" or the equivalent. Fixing it to recognize
CC_FOR_TARGET is on my list somewhere.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-05-28 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 19:46 H. J. Lu
2003-05-26 19:59 ` Daniel Jacobowitz
2003-05-26 20:16 ` H. J. Lu
2003-05-27 14:46 ` Elena Zannoni
2003-05-27 14:58 ` H. J. Lu
2003-05-27 15:05 ` Daniel Jacobowitz
2003-05-27 15:06 ` Elena Zannoni
2003-05-27 15:19 ` H. J. Lu
2003-05-28 16:47 ` David Carlton
2003-05-28 16:50 ` Daniel Jacobowitz [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=20030528165012.GA3644@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@math.stanford.edu \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).