From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org, baruchel@gmx.com
Subject: Re: Recursive call to stepi and "Max user call depth exceeded"
Date: Fri, 04 Nov 2011 17:23:00 -0000 [thread overview]
Message-ID: <201111041723.22991.pedro@codesourcery.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2011-11-04 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 17:04 Thomas Baruchel
2011-11-04 17:23 ` Pedro Alves [this message]
2011-11-04 17:47 ` Run until some FPU register has changed Thomas Baruchel
2011-11-04 17:55 ` Jonas Maebe
2011-11-04 18:37 ` Pedro Alves
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=201111041723.22991.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=baruchel@gmx.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