public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "J. Johnston" <jjohnstn@redhat.com>
To: gdb@sources.redhat.com
Subject: prev_pc problem on ia64
Date: Fri, 11 Apr 2003 22:21:00 -0000	[thread overview]
Message-ID: <3E973FEB.1090500@redhat.com> (raw)

I am running into a problem on ia64 regarding performing a next
after an inferior function call or after using "return" from
a function.

What's occurring is that an inferior function call ends up setting
the static prev_pc value in infrun.c: stop_stepping().  When we
return to the gdb prompt prev_pc is not restored to its original
value.  A similar problem occurs when we return from a function
using the gdb return command.

On the ia64, there are extraneous line table entries that do not
increase the line number.  When we perform a next after the inferior
call, we step until the line number changes from the one set for
prev_pc.  Unfortunately, this only gets us part way through the line as
we run until the next line table entry.

For the x86, this problem does not crop up in the test case I am looking
at because there are none of these additional line table entries.  When
we perform a next, it finds the next line regardless of the fact that prev_pc is
not correctly set.

The following is an example of the line table entries I am talking about on
the ia64 (generated by readelf -wl).  I am using a recent gcc but this behavior
also occurs for gcc 2.96

   Special opcode 20: advance Address by 1 to 0x40000000000007e1 and Line by 1 to 31
   Special opcode 215: advance Address by 15 to 0x40000000000007f0 and Line by 0 to 31
   Special opcode 19: advance Address by 1 to 0x40000000000007f1 and Line by 0 to 31
   Special opcode 19: advance Address by 1 to 0x40000000000007f2 and Line by 0 to 31
   Special opcode 201: advance Address by 14 to 0x4000000000000800 and Line by 0 to 31
   Special opcode 20: advance Address by 1 to 0x4000000000000801 and Line by 1 to 32
   Special opcode 243: advance Address by 17 to 0x4000000000000812 and Line by 0 to 32
   Special opcode 201: advance Address by 14 to 0x4000000000000820 and Line by 0 to 32
   Special opcode 19: advance Address by 1 to 0x4000000000000821 and Line by 0 to 32
   Special opcode 19: advance Address by 1 to 0x4000000000000822 and Line by 0 to 32
   Special opcode 201: advance Address by 14 to 0x4000000000000830 and Line by 0 to 32
   Special opcode 19: advance Address by 1 to 0x4000000000000831 and Line by 0 to 32

Same function compiled for i686:

   Special opcode 76: advance Address by 5 to 0x804839e and Line by 1 to 31
   Special opcode 230: advance Address by 16 to 0x80483ae and Line by 1 to 32
   Special opcode 146: advance Address by 10 to 0x80483b8 and Line by 1 to 33
   Special opcode 160: advance Address by 11 to 0x80483c3 and Line by 1 to 34

I have a patch whereby I reset prev_pc in infrun.c:init_execution_control_state():

   if (prev_pc != 0)
     prev_pc = read_pc ();

prior to setting the ecs->sal.  This works for me in both scenarios.  The check for
0 was needed because I get a failure on the ia64 trying to read the pc too early when
the psr register was invalid.

This may or may not be the best way of doing this.  Any other platforms experiencing
this problem in call-ar-st.exp or return.exp?

-- Jeff J.

             reply	other threads:[~2003-04-11 22:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 22:21 J. Johnston [this message]
2003-04-14 20:17 ` Elena Zannoni
2003-04-14 20:42   ` J. Johnston
2003-04-15 22:06   ` Andrew Cagney
2003-04-16  0:04     ` J. Johnston
2003-04-16  1:35       ` Elena Zannoni
2003-04-16  1:56         ` Andrew Cagney
2003-04-16  3:17           ` Andrew Cagney
2003-04-16 15:14             ` J. Johnston
2003-05-05 19:57             ` J. Johnston

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=3E973FEB.1090500@redhat.com \
    --to=jjohnstn@redhat.com \
    --cc=gdb@sources.redhat.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).