Re: gdb unable to print fn argument correctly

Daniel Jacobowitz
2005-07-27T18:10:08Z

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).