From: Mark Kettenis <kettenis@chello.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC/RFA] Print in-memory struct return values
Date: Fri, 07 May 2004 23:10:00 -0000 [thread overview]
Message-ID: <200405072310.i47NA5ld013878@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <409C0F30.4090409@gnu.org> (message from Andrew Cagney on Fri, 07 May 2004 18:35:28 -0400)
Date: Fri, 07 May 2004 18:35:28 -0400
From: Andrew Cagney <cagney@gnu.org>
> The current GDB doesn't print the return value when using `finish' for
> functions return structures that are not returned in registers. Note
> that this is a regression from GDB 6.0 for many systems. Anyway, the
> attached patch provides a way to fix this, and adds the necessary
> support to the i386 target.
>
> If there are no comments, I'll check this in in a few days. Eli, is
> the doc bit OK?
Why not add another member to `enum return_value_convention' so that
return_value() can directly differentate between these two cases?
I thought about that. Returning an address from gdbarch_return_value
is a bit weird. Hmm, it just occurs to me that we make a copy of the
value and have gdbarch_return_value return that. Hmm, back to the
drawing board. Expect a new patch soon.
Mark
next prev parent reply other threads:[~2004-05-07 23:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-07 17:07 Mark Kettenis
2004-05-07 22:35 ` Andrew Cagney
2004-05-07 23:10 ` Mark Kettenis [this message]
2004-05-08 19:58 ` Mark Kettenis
2004-05-12 17:47 ` Michael Snyder
2004-05-15 21:26 ` Mark Kettenis
2004-05-15 22:12 ` Andreas Schwab
2004-05-16 10:28 ` Mark Kettenis
[not found] ` <200405081958.i48JwlUU000353@elgar.kettenis.dyndns.org>
[not found] ` <409D4216.4050401@gnu.org>
[not found] ` <200405082101.i48L1NUK000503@elgar.kettenis.dyndns.org>
2004-05-08 21:14 ` Andrew Cagney
2004-05-08 23:02 ` Mark Kettenis
2004-05-09 13:59 ` Andrew Cagney
2004-05-09 14:03 ` Mark Kettenis
2004-05-11 23:53 ` Andrew Cagney
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=200405072310.i47NA5ld013878@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=cagney@gnu.org \
--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