From: Doug Evans <dje@google.com>
To: Haitao Dan <dan.haitao@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Trace each statement
Date: Sat, 18 Dec 2010 18:19:00 -0000 [thread overview]
Message-ID: <AANLkTikbtREaPB-eiRYXNQEeK-qZFZHZQ_7DQva4aGRL@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=Heh8ispZu_Sywa3U8PiS5QVDv6tX5UHJd8nB3@mail.gmail.com>
On Thu, Dec 16, 2010 at 3:37 AM, Haitao Dan <dan.haitao@gmail.com> wrote:
> Dear All,
>
> Is there a way to output the execution path of the run of a c program using GDB?
>
> Thank you very much!
This is a simplistic example that can be built on if you want.
$ cat trace-prog.c
int x;
int
main ()
{
int i;
for (i = 0; i < 10; ++i)
x += i;
return 0;
}
$ cat trace-prog.gdb
# -*- python -*-
python
gdb.execute ("start")
while True:
try:
gdb.execute ("step")
except:
break
$ gcc -g trace-prog.c -o trace-prog
$ ./gdb --batch -q -x trace-prog.gdb trace-prog.x32
Temporary breakpoint 1 at 0x80483a5: file trace-prog.c, line 9.
Temporary breakpoint 1, main () at trace-prog.c:9
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
10 x += i;
9 for (i = 0; i < 10; ++i)
12 return 0;
13 }
0x0048f6e5 in __libc_start_main () from /lib/libc.so.6
Single stepping until exit from function __libc_start_main,
which has no line number information.
Program exited normally.
$
next prev parent reply other threads:[~2010-12-18 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 11:37 Haitao Dan
2010-12-18 18:19 ` Doug Evans [this message]
2010-12-18 18:21 ` Doug Evans
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=AANLkTikbtREaPB-eiRYXNQEeK-qZFZHZQ_7DQva4aGRL@mail.gmail.com \
--to=dje@google.com \
--cc=dan.haitao@gmail.com \
--cc=gdb@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