From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: two Ada tests -vs- debug-file-directory
Date: Mon, 05 Mar 2012 21:55:00 -0000 [thread overview]
Message-ID: <20120305215445.GL2853@adacore.com> (raw)
In-Reply-To: <87ipiivj5s.fsf@fleche.redhat.com>
> I've attached gdb.log for a failing run of the two tests.
Thank you!
For the first test (mi_task_arg.exp), the failure is indeed caused
by the fact that a function in the callstack for which there is normally
no debugging info (and thus no parameters in the backtrace) now has
debug info, and starts showing parameters for that frame. Your fix
prevents that from happening, and is just as good as allowing the
parameters in the output from the -stack-list-arguments command.
For the second testcase, the debugger picks up a wack load of functions
that fit the profile of a function we are trying to break into (Ada
operator "+", for instance). So we end up with more locations than
we expected. The fix you provided is the only reasonable fix in this
case.
So I wouldn't change a thing :).
--
Joel
prev parent reply other threads:[~2012-03-05 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 20:57 Tom Tromey
2012-03-05 21:04 ` Joel Brobecker
2012-03-05 21:21 ` Tom Tromey
2012-03-05 21:55 ` 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=20120305215445.GL2853@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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