This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Recursive call to stepi and "Max user call depth exceeded"
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb at sourceware dot org, baruchel at gmx dot com
- Date: Fri, 4 Nov 2011 17:23:22 +0000
- Subject: Re: Recursive call to stepi and "Max user call depth exceeded"
- References: <alpine.DEB.2.02.1111041800100.16277@lili-Inspiron-1525>
On Friday 04 November 2011 17:03:53, Thomas Baruchel wrote:
> Hi,
>
> I tried to use the following trick:
>
> define s
> info float
> stepi
> s
> end
>
> (based on an idea found there:
> http://stackoverflow.com/questions/7940963/trace-application-compiled-by-gcc )
>
> But I soon encountered the error:
> Max user call depth exceeded -- command aborted.
>
> What I am trying to do is: print the fpu register after each machine instruction
> (of course output is parsed by an external program), but using a recursive
> function obviously is a bad idea. How can I run my program step by step
> and print the fpu after each step? Regards,
Right, don't make the command recursive. That was bogus advice.
(gdb) define mystepi
> si
> info float
> end
(gdb) while 1
> mystepi
> end
Or instead:
(gdb) define hook-stop
> info float
> end
(gdb) while 1
> si
> end
--
Pedro Alves