From: Andreas Schwab <schwab@suse.de>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Fix frame-args.exp failure
Date: Wed, 28 May 2008 14:09:00 -0000 [thread overview]
Message-ID: <jelk1vlfl0.fsf@sykes.suse.de> (raw)
In-Reply-To: <200805271816.m4RIGO4D022560@d12av02.megacenter.de.ibm.com> (Ulrich Weigand's message of "Tue, 27 May 2008 20:16:24 +0200 (CEST)")
"Ulrich Weigand" <uweigand@de.ibm.com> writes:
> Andreas Schwab wrote:
>
>> Daniel Jacobowitz <drow@false.org> writes:
>> > Wouldn't this make any optimized-out locals be treated like frame
>> > arguments? And also see print_frame_arg_vars. I thought there was an
>> > "is an argument" flag on variables nowadays but it doesn't look like
>> > it.
>>
>> How about this instead? Tested on ppc-linux.
>
> Did you get a chance to test with non-DWARF-2 debug info as well
> (at least stabs would be nice to test)?
I did some checks using the frame-args test with -gstabs. It has a
different issue in that the arguments s and u are shown, but with bogus
contents (but this is not a regression).
> ... these, which appear to be unrelated changes?
Oops, forgot to clean them out. (There is a bug about calling objc
methods which I was also working on, but those changes don't fix it
yet.)
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2008-05-27 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 21:26 Andreas Schwab
2008-05-22 21:51 ` Daniel Jacobowitz
2008-05-23 3:05 ` Andreas Schwab
2008-05-27 18:37 ` Andreas Schwab
2008-05-27 19:11 ` Ulrich Weigand
2008-05-27 20:06 ` Daniel Jacobowitz
2008-05-29 20:45 ` Ulrich Weigand
2008-05-29 21:33 ` Daniel Jacobowitz
2008-05-28 14:09 ` Andreas Schwab [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=jelk1vlfl0.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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