From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9519 invoked by alias); 11 Nov 2005 09:59:58 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 9483 invoked by uid 22791); 11 Nov 2005 09:59:55 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 11 Nov 2005 09:59:55 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id jAB9xsIM025328 for ; Fri, 11 Nov 2005 04:59:54 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id jAB9xsV24453; Fri, 11 Nov 2005 04:59:54 -0500 Received: from theseus.home..redhat.com (vpn26-2.sfbay.redhat.com [172.16.26.2]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id jAB9xht2009365; Fri, 11 Nov 2005 04:59:45 -0500 To: Wu Zhou Cc: Mark Kettenis , gdb@sources.redhat.com Subject: Re: The root cause for SEGV in evaluating fortran function call, any solution or suggestion? References: <20051102145258.GA28372@nevyn.them.org> <200511032134.jA3LYDsT017248@elgar.sibelius.xs4all.nl> <20051107000949.GD19200@nevyn.them.org> <20051110005913.GA10619@nevyn.them.org> From: Jim Blandy Date: Fri, 11 Nov 2005 09:59:00 -0000 In-Reply-To: <20051110005913.GA10619@nevyn.them.org> (Daniel Jacobowitz's message of "Wed, 9 Nov 2005 19:59:13 -0500") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-11/txt/msg00224.txt.bz2 Daniel Jacobowitz writes: > On Wed, Nov 09, 2005 at 04:55:27PM -0800, Jim Blandy wrote: >> >> Daniel Jacobowitz 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.