From: Daniel Jacobowitz <drow@false.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb unable to print fn argument correctly
Date: Wed, 27 Jul 2005 18:10:00 -0000 [thread overview]
Message-ID: <20050727180958.GA14088@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0507261310420.21929@lazy>
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
prev parent reply other threads:[~2005-07-27 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 20:06 Manoj Iyer
2005-07-21 20:10 ` Daniel Jacobowitz
2005-07-21 22:55 ` Manoj Iyer
2005-07-21 22:59 ` Daniel Jacobowitz
2005-07-26 18:44 ` Manoj Iyer
2005-07-27 18:10 ` Daniel Jacobowitz [this message]
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=20050727180958.GA14088@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.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).