From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: More "catch assert" Ada failures
Date: Mon, 04 Jun 2007 16:06:00 -0000 [thread overview]
Message-ID: <20070604160600.GA8815@caradoc.them.org> (raw)
In-Reply-To: <20070604155009.GF3761@adacore.com>
On Mon, Jun 04, 2007 at 08:50:09AM -0700, Joel Brobecker wrote:
> > Debian now has a libgnat-4.1-dbg package which includes complete
> > debugging information for libgnat; this should let GDB handle
> > exception and assertion catchpoints. A couple of the tests fail
> > though:
> >
> > Unable to break on 'system__assertions__raise_assert_failure' in this
> > configuration.
>
> I indeed see some FAILs on that test, but ldd reports that the program
> is still linked against libgnat-4.1.so.1, not the one installed in
> /usr/lib/debug/usr/lib. I tried setting up symbolic links from one to
> the other, but then the compiler crashes. Did you run the testsuite
> with some specific switches?
You need to configure with --prefix=/usr, and then GDB will pick up
files in /usr/lib/debug automatically. I get:
FAIL: gdb.ada/catch_ex.exp: insert catchpoint on failed assertions
FAIL: gdb.ada/catch_ex.exp: info break, second run
FAIL: gdb.ada/catch_ex.exp: continuing to failed assertion
FAIL: gdb.ada/catch_ex.exp: continuing to unhandled exception (the
program exited)
FAIL: gdb.ada/catch_ex.exp: continuing to program completion (the
program is no longer running)
Without that I get twelve failures and no passes.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-04 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 13:02 Daniel Jacobowitz
2007-06-04 15:49 ` Joel Brobecker
2007-06-04 16:06 ` Daniel Jacobowitz [this message]
2007-06-04 19:06 ` Joel Brobecker
2007-06-04 21:30 ` Joel Brobecker
2007-06-04 21:57 ` Daniel Jacobowitz
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=20070604160600.GA8815@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--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