Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Trace each statement
@ 2010-12-16 11:37 Haitao Dan
  2010-12-18 18:19 ` Doug Evans
  0 siblings, 1 reply; 3+ messages in thread
From: Haitao Dan @ 2010-12-16 11:37 UTC (permalink / raw)
  To: gdb

Dear All,

Is there a way to output the execution path of the run of a c program using GDB?

Thank you very much!

Best regards,

Dan


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Trace each statement
  2010-12-16 11:37 Trace each statement Haitao Dan
@ 2010-12-18 18:19 ` Doug Evans
  2010-12-18 18:21   ` Doug Evans
  0 siblings, 1 reply; 3+ messages in thread
From: Doug Evans @ 2010-12-18 18:19 UTC (permalink / raw)
  To: Haitao Dan; +Cc: gdb

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.
$


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Trace each statement
  2010-12-18 18:19 ` Doug Evans
@ 2010-12-18 18:21   ` Doug Evans
  0 siblings, 0 replies; 3+ messages in thread
From: Doug Evans @ 2010-12-18 18:21 UTC (permalink / raw)
  To: Haitao Dan; +Cc: gdb

On Sat, Dec 18, 2010 at 10:19 AM, Doug Evans <dje@google.com> wrote:
> 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.

Heh, setting aside the fact that I can't cut-n-paste very well.

> $ gcc -g trace-prog.c -o trace-prog
> $ ./gdb --batch -q -x trace-prog.gdb trace-prog.x32

Add or remove the .x32 suffix as you wish.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-12-18 18:21 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-12-16 11:37 Trace each statement Haitao Dan
2010-12-18 18:19 ` Doug Evans
2010-12-18 18:21   ` Doug Evans

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox