From: Hannes Domani <ssbssa@yahoo.de>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC][PATCH 0/6] Step program considering the source column information
Date: Tue, 19 May 2020 16:02:14 +0000 (UTC) [thread overview]
Message-ID: <1207867761.770219.1589904134307@mail.yahoo.com> (raw)
In-Reply-To: <ab0d525f-4318-fc80-c0e6-225a95c778ea@linaro.org>
Am Dienstag, 19. Mai 2020, 14:27:44 MESZ hat Luis Machado <luis.machado@linaro.org> Folgendes geschrieben:
> Thanks for working on this, it is really useful.
>
> I'm guessing this series would probably handle the following situation
> very well:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=21221
According to the debug info, the i initialization is on line 5, column 23.
And the rest of the for-loop is on line 5, column 5.
With the new column-based next-command, it goes back and forth between
them (but you have to wait a while for the inner loop to finish).
Debug session:
(gdb) start
Temporary breakpoint 1 at 0x40162d: file gdb-21221.c, line 5, column 23.
Starting program: C:\src\tests\gdb-21221.exe
Temporary breakpoint 1, main () at gdb-21221.c:5
5 for (unsigned int i = 0U; i < 0xFFFFFU; i++)
^
(gdb) nc
5 for (unsigned int i = 0U; i < 0xFFFFFU; i++)
^
(gdb) nc
5 for (unsigned int i = 0U; i < 0xFFFFFU; i++)
^
(gdb) nc
5 for (unsigned int i = 0U; i < 0xFFFFFU; i++)
^
(gdb) l
1 int main (void)
2 {
3 while (1)
4 {
5 for (unsigned int i = 0U; i < 0xFFFFFU; i++)
6 {
7 ;
8 }
9 }
10 }
(gdb) disas
Dump of assembler code for function main:
0x0000000000401620 <+0>: push %rbp
0x0000000000401621 <+1>: mov %rsp,%rbp
0x0000000000401624 <+4>: sub $0x30,%rsp
0x0000000000401628 <+8>: callq 0x401700 <__main>
0x000000000040162d <+13>: movl $0x0,-0x4(%rbp)
0x0000000000401634 <+20>: jmp 0x40163a <main+26>
0x0000000000401636 <+22>: addl $0x1,-0x4(%rbp)
0x000000000040163a <+26>: cmpl $0xffffe,-0x4(%rbp)
0x0000000000401641 <+33>: jbe 0x401636 <main+22>
0x0000000000401643 <+35>: jmp 0x40162d <main+13>
End of assembler dump.
(gdb) maint info line-table gdb-21221.c
objfile: C:\src\tests\gdb-21221.exe ((struct objfile *) 0x11f4e670)
compunit_symtab: ((struct compunit_symtab *) 0x11f71890)
symtab: C:\src\tests\gdb-21221.c ((struct symtab *) 0x11f71910)
linetable: ((struct linetable *) 0x1204fde0):
INDEX LINE COLUMN ADDRESS IS-STMT
0 2 1 0x0000000000401620 Y
1 2 1 0x0000000000401628 Y
2 5 23 0x000000000040162d Y
3 5 5 0x0000000000401634 Y
4 END 0x0000000000401645 Y
next prev parent reply other threads:[~2020-05-19 16:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200516172632.4803-1-ssbssa.ref@yahoo.de>
2020-05-16 17:26 ` Hannes Domani
2020-05-16 17:26 ` [PATCH 1/6] Add column information of dwarf to the symbol information Hannes Domani
2020-05-18 16:17 ` Tom Tromey
2020-05-19 12:23 ` Luis Machado
2020-05-16 17:26 ` [PATCH 2/6][PR gdb/25913] Implement nextc and stepc commands Hannes Domani
2020-05-16 17:26 ` [PATCH 3/6] Add column information to maint info line-table Hannes Domani
2020-05-16 17:26 ` [PATCH 4/6] Add LineTableEntry.column to python line table interface Hannes Domani
2020-05-27 13:50 ` Tom de Vries
2020-05-27 14:36 ` Tom Tromey
2020-05-16 17:26 ` [PATCH 5/6][PR gdb/25911] Show column of current execution point in frame info Hannes Domani
2020-05-18 16:20 ` Tom Tromey
2020-05-18 16:37 ` Hannes Domani
2020-05-19 14:51 ` Tom Tromey
2020-05-16 17:26 ` [PATCH 6/6] Show column of current execution point in TUI Hannes Domani
2020-05-16 18:45 ` [RFC][PATCH 0/6] Step program considering the source column information Pedro Alves
2020-05-17 0:08 ` Hannes Domani
2020-05-18 16:21 ` Tom Tromey
2020-05-18 16:28 ` Hannes Domani
2020-05-19 12:27 ` Luis Machado
2020-05-19 16:02 ` Hannes Domani [this message]
2020-05-27 15:33 ` Tom de Vries
2020-05-27 16:04 ` Hannes Domani
2020-06-02 9:08 ` Tom de Vries
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=1207867761.770219.1589904134307@mail.yahoo.com \
--to=ssbssa@yahoo.de \
--cc=gdb-patches@sourceware.org \
/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