[Bug gdb/12938] RFE: Find the regression point in the code

["pedro at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=12938

Pedro Alves <pedro at codesourcery dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pedro at codesourcery dot
                   |                            |com

--- Comment #1 from Pedro Alves <pedro at codesourcery dot com> 2011-06-28 10:02:58 UTC ---
A while ago someone posted
<http://comments.gmane.org/gmane.comp.gdb.devel/27441>
showing an approach for this use case that builds on top of gdb, rather than
built in:

"(...) which was written to run two gdb's debugging a stage1 and
stage2 generation of a compiler and single step until a line number differs.
It is written in Python and uses pexpect"

>From tgdb-0.1.tar.gz's README.

"TwinGDB is a front end to GDB which runs two instances of gdb on two
executables and will automatically single step them until a deviation
(seen by line number) occurs.  Typically this is useful if you are
developing a program for a different archicture or if you are in
compiler development where a second generation build fails to behave
in exactly the same way as the first generation.  It can also be used
to explore when a particular command line option takes effect.  There
are probably more uses as well..

This program is in a pre alpha state, nevetheless, the author uses
it to debug GNU Modula-2.

As single stepping gdb is not exactly fast, the program can be
configured to skip functions, skip source files which reside in
particular directories, start stepping at a particular function and
finish at another etc."

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.