public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
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: Thu, 21 Jul 2005 22:59:00 -0000	[thread overview]
Message-ID: <20050721225943.GA22858@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0507211718490.620@lazy>

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.

>               Line Column   Address  File
>               ---- ------   -------  ----
>            1     3    0   0x100004e4 test1.c
>            2     4    0   0x10000510 test1.c
>            3     5    0   0x10000538 test1.c
>            4     9    0   0x10000560 test1.c
>            5    10    0   0x10000574 test1.c
>            6    11    0   0x1000057c test1.c
>            7    12    0   0x10000588 test1.c
>            8    13    0   0x10000594 test1.c
>            9    14    0   0x10000598 test1.c

If this is GCC output, then there ought to be two lines in each
function, the second marking the end of the prologue.  Figure out why
there's only one in each of your small functions.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-07-21 22:59 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 [this message]
2005-07-26 18:44       ` Manoj Iyer
2005-07-27 18:10         ` 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=20050721225943.GA22858@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).