From: Jim Blandy <jimb@redhat.com>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sources.redhat.com
Subject: Re: The root cause for SEGV in evaluating fortran function call, any solution or suggestion?
Date: Fri, 11 Nov 2005 09:59:00 -0000 [thread overview]
Message-ID: <vt2hdaj5wtu.fsf@theseus.home.> (raw)
In-Reply-To: <20051110005913.GA10619@nevyn.them.org> (Daniel Jacobowitz's message of "Wed, 9 Nov 2005 19:59:13 -0500")
Daniel Jacobowitz <drow@false.org> writes:
> On Wed, Nov 09, 2005 at 04:55:27PM -0800, Jim Blandy wrote:
>>
>> Daniel Jacobowitz <drow@false.org> writes:
>> > Maybe if you pass the sp value by reference to value_arg_coerce and
>> > adjust it there...
>>
>> Or you could pass a regcache.
>
> We're not trying to adjust the saved sp in the regcache, but the
> interim SP being used in setting up the function - it's not in the
> regcache until much later (after push_dummy_call).
My thought was that a language-specific value_arg_coerce might need to
do all manner of strange things, perhaps affecting other registers.
It's really all of infcall.c that is C-specific. But I may be getting
ahead of myself.
next prev parent reply other threads:[~2005-11-11 9:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 10:14 [GDB & Fortran] Anyone has success experience with printing the result of Fortran function calls? Wu Zhou
2005-11-02 2:39 ` The root cause for SEGV in evaluating fortran function call, any solution or suggestion? Wu Zhou
2005-11-02 14:53 ` Daniel Jacobowitz
2005-11-03 3:12 ` Wu Zhou
2005-11-03 21:34 ` Mark Kettenis
2005-11-04 3:15 ` Wu Zhou
2005-11-04 3:52 ` Wu Zhou
2005-11-07 0:09 ` Daniel Jacobowitz
2005-11-07 4:49 ` Wu Zhou
2005-11-07 5:01 ` Daniel Jacobowitz
2005-11-07 5:16 ` Wu Zhou
2005-11-10 0:55 ` Jim Blandy
2005-11-10 0:59 ` Daniel Jacobowitz
2005-11-11 9:59 ` Jim Blandy [this message]
2005-11-04 11:20 ` Dave Korn
2005-11-06 23:58 ` Daniel Jacobowitz
2005-11-02 15:51 ` Mark Kettenis
2005-11-03 2:50 ` Wu Zhou
2005-11-03 7:42 ` Jim Blandy
2005-11-03 10:16 ` Wu Zhou
2005-11-07 0:02 ` Daniel Jacobowitz
2005-11-10 0:49 ` Jim Blandy
2005-11-10 1:00 ` 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=vt2hdaj5wtu.fsf@theseus.home. \
--to=jimb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=woodzltc@cn.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).