From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21787 invoked by alias); 27 Jul 2005 18:10:08 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 21749 invoked by uid 22791); 27 Jul 2005 18:10:02 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 27 Jul 2005 18:10:02 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1DxqLv-0003hU-3h; Wed, 27 Jul 2005 14:09:59 -0400 Date: Wed, 27 Jul 2005 18:10:00 -0000 From: Daniel Jacobowitz To: Manoj Iyer Cc: gdb@sources.redhat.com Subject: Re: gdb unable to print fn argument correctly Message-ID: <20050727180958.GA14088@nevyn.them.org> Mail-Followup-To: Manoj Iyer , gdb@sources.redhat.com References: <20050721201010.GA18155@nevyn.them.org> <20050721225943.GA22858@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-07/txt/msg00247.txt.bz2 On Tue, Jul 26, 2005 at 01:17:01PM -0500, Manoj Iyer wrote: > > > > > On Thu, Jul 21, 2005 at 05:29:10PM -0500, Manoj Iyer wrote: > > > GDB stopped on the instruction at 0x...10000544, which is 10000544: d8 > > > 3f 00 70 stfd f1,112(r31). > > > > The prologue analyzer must have been invoked. One way to fix the > > problem would be to find out why the prologue analyzer stopped before > > this instruction. Search for skip_prologue. > > > > Looks like skip_prolog was called consistantly on both working and > non-working cases. Below is the output from GDB... > rs6000-tdep.c: rs6000_skip_prologue(): 501 :: pc = 0x10000538 The prologue analyzer thinks the prologue stops rather earlier than it really does. > Also, another question I have is, in utils.c, wrap_here(), where does the > wrap_buffer gets initialized? > > if (wrap_buffer[0]) > { > *wrap_pointer = '\0'; > fputs_unfiltered (wrap_buffer, gdb_stdout); > } > > prints the arguments to the function among other things, so I am trying to > identify who fills the wrap_buffer with information. Grep for wrap_buffer? fputs_maybe_filtered copies data into wrap_buffer (via wrap_pointer). -- Daniel Jacobowitz CodeSourcery, LLC