From: William Tambe <tambewilliam@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb@sourceware.org
Subject: Re: gdb command "next" wrongly working as command "step"
Date: Sat, 24 Aug 2019 03:36:00 -0000 [thread overview]
Message-ID: <CAF8i9mOgK6C8P5xnqJCyiy6dFJttB9ofR0w-W-RYnns8OHi4-g@mail.gmail.com> (raw)
In-Reply-To: <ca3b5f71-7493-6d63-e1c2-e74cd48583a8@redhat.com>
On Fri, Aug 23, 2019 at 4:54 PM Pedro Alves <palves@redhat.com> wrote:
>
> On 8/23/19 10:33 PM, William Tambe wrote:
> > On Sun, Aug 18, 2019 at 4:06 AM Jan Kratochvil
> > <jan.kratochvil@redhat.com> wrote:
> >> On Sun, 18 Aug 2019 10:31:54 +0200, William Tambe wrote:
> >>> Can I have suggestions of locations within the gdb code where I could
> >>> put breakpoints to trace where the issue I am having is occurring ?
> >> Check what "set debug infrun 1" says and grep the sources for the displayed
> >> messages.
> >>
> > Using "set debug infrun 1", I can see that GDB stops only after
> > printing the following message:
> > infrun: stepped to a different line.
> > When the above event happens, GDB has stepped inside the function,
> > which is obviously going to be on a different line; however, I am
> > expecting GDB to step over the function.
>
> Do a backtrace at this point. GDB should see the caller in frame #1.
> Sounds like it doesn't.
It does.
My backtrace appear to be working properly.
See below example listing from using "next" at a line where a function
is used; it also show the output of "bt" before and after using
"next".
The decoded instructions is a lot of noise, but I am hoping you could
see that I have a working backtracing, but yet "next" is working as
though it was "step".
(gdb) b _puts_r
Breakpoint 1 at 0x1688: file
../../../../../newlib-cygwin/newlib/libc/stdio/puts.c, line 73.
(gdb) r
Starting program: a.out
Breakpoint 1, _puts_r (ptr=0x8b48 <impure_data>, s=0x7b20 "Hello
World") at ../../../../../newlib-cygwin/newlib/libc/stdio/puts.c:73
73 size_t c = strlen (s);
c7 2e => 0x00001688 <_puts_r+24>: cpy %2, %fp
9f 2c 0x0000168a <_puts_r+26>: inc8 %2, -4
8c 18 0x0000168c <_puts_r+28>: li8 %1, 0xc8 # -56
b8 1e 0x0000168e <_puts_r+30>: add %1, %fp
f2 21 0x00001690 <_puts_r+32>: st32 %2, %1
c7 1e 0x00001692 <_puts_r+34>: cpy %1, %fp
9c 1c 0x00001694 <_puts_r+36>: inc8 %1, -52
ea 11 0x00001696 <_puts_r+38>: ld32 %1, %1
e0 d0 0x00001698 <_puts_r+40>: gip %sr
a2 d0 be 01 00 00 0x0000169a <_puts_r+42>: inc32 %sr, 446
d8 fd 0x000016a0 <_puts_r+48>: jl %rp, %sr
8c 38 0x000016a2 <_puts_r+50>: li8 %3, 0xc8 # -56
b8 3e 0x000016a4 <_puts_r+52>: add %3, %fp
ea 33 0x000016a6 <_puts_r+54>: ld32 %3, %3
f2 13 0x000016a8 <_puts_r+56>: st32 %1, %3
(gdb) bt
#0 _puts_r (ptr=0x8b48 <impure_data>, s=0x7b20 "Hello World") at
../../../../../newlib-cygwin/newlib/libc/stdio/puts.c:73
#1 0x0000184a in puts (s=0x7b20 "Hello World") at
../../../../../newlib-cygwin/newlib/libc/stdio/puts.c:129
#2 0x0000132e in main (argc=1, argv=0x3fff000) at helloworld.c:5
(gdb) n
strlen (str=0x7b20 "Hello World") at
../../../../../newlib-cygwin/newlib/libc/string/strlen.c:54
54 const char *start = str;
c7 1e => 0x00001866 <strlen+14>: cpy %1, %fp
9f 18 0x00001868 <strlen+16>: inc8 %1, -8
c7 2e 0x0000186a <strlen+18>: cpy %2, %fp
9f 24 0x0000186c <strlen+20>: inc8 %2, -12
ea 32 0x0000186e <strlen+22>: ld32 %3, %2
f2 31 0x00001870 <strlen+24>: st32 %3, %1
(gdb) bt
#0 strlen (str=0x7b20 "Hello World") at
../../../../../newlib-cygwin/newlib/libc/string/strlen.c:54
#1 0x000016a2 in _puts_r (ptr=0x8b48 <impure_data>, s=0x7b20 "Hello
World") at ../../../../../newlib-cygwin/newlib/libc/stdio/puts.c:73
#2 0x0000184a in puts (s=0x7b20 "Hello World") at
../../../../../newlib-cygwin/newlib/libc/stdio/puts.c:129
#3 0x0000132e in main (argc=1, argv=0x3fff000) at helloworld.c:5
(gdb)
>
> Or to be more accurate, use "stepi" to step to the first instruction
> of the called function, and run "bt" there.
I have also tried using "stepi" to step to the first instruction of
the called function.
"bt" works correctly.
>
> As Jan said, for "next" to work properly, backtrace/unwinding must work
> properly. When "next" behaves like "step", the most frequent reason
> is that unwinding is broken. "next" does a "backtrace" to detect whether
> you've stepped into called function, and if you did, then it continues
> execution to the address where the called function returns.
>
> Thanks,
> Pedro Alves
next prev parent reply other threads:[~2019-08-24 3:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 3:36 William Tambe
2019-08-18 4:16 ` Jan Kratochvil
2019-08-18 8:32 ` William Tambe
2019-08-18 9:06 ` Jan Kratochvil
2019-08-23 21:33 ` William Tambe
2019-08-23 21:54 ` Pedro Alves
2019-08-24 3:36 ` William Tambe [this message]
2019-08-25 19:04 ` William Tambe
2019-08-26 13:18 ` Pedro Alves
2019-09-01 19:06 ` William Tambe
2019-09-05 11:59 ` Andrew Burgess
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=CAF8i9mOgK6C8P5xnqJCyiy6dFJttB9ofR0w-W-RYnns8OHi4-g@mail.gmail.com \
--to=tambewilliam@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@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).