public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: gdb-patches@sourceware.org
Subject: [RFC][PATCH 0/6] Step program considering the source column information
Date: Sat, 16 May 2020 19:26:27 +0200	[thread overview]
Message-ID: <20200516172632.4803-1-ssbssa@yahoo.de> (raw)
In-Reply-To: <20200516172632.4803-1-ssbssa.ref@yahoo.de>

Basically, this implements the new commands nextc (nc) and stepc (sc),
which allow to step through the program until an instruction is reached,
that belongs to another source column (according to the debug information).

The current column location is visualized in the frame info, and in the TUI.

Also, the column information is added to 'maint info line-table' and the
python line table interface.

Since the frame info output is different, this certainly breaks the
testsuite, so this column indicator needs a parameter to disable, but I
wasn't concerned about this yet.

With the example code from PR25913, it looks like this:

(gdb) start
Temporary breakpoint 2 at 0x40162d: file gdb-25911.c, line 4.
Starting program: C:\src\tests\gdb-25911.exe

Temporary breakpoint 2, main () at gdb-25911.c:4
4         int a = 4;
              ^
(gdb) nc
6         a = 5; a = 6; a = 7;
            ^
(gdb) nc
6         a = 5; a = 6; a = 7;
                   ^
(gdb) nc
6         a = 5; a = 6; a = 7;
                          ^
(gdb) nc
8         return 0;


What do you think of this so far?


[PATCH 1/6] Add column information of dwarf to the symbol information
[PATCH 2/6] Implement nextc and stepc commands (PR gdb/25913)
[PATCH 3/6] Add column information to maint info line-table
[PATCH 4/6] Add LineTableEntry.column to python line table interface
[PATCH 5/6] Show column of current execution point in frame info (PR
[PATCH 6/6] Show column of current execution point in TUI


       reply	other threads:[~2020-05-16 17:28 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 [this message]
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
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=20200516172632.4803-1-ssbssa@yahoo.de \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).