public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug external/13207] New: Provide a script to advance two versions of a program and find where they diverge. Date: Tue, 20 Sep 2011 21:49:00 -0000 [thread overview] Message-ID: <bug-13207-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13207 Bug #: 13207 Summary: Provide a script to advance two versions of a program and find where they diverge. Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: external AssignedTo: unassigned@sourceware.org ReportedBy: dje@google.com Classification: Unclassified Sometimes one has a debugging situation where a program worked yesterday, it doesn't work today, and it's taking awhile to figure out where the breakage is. IWBN to have a script that could advance two versions of a program and find where they diverge. Determining divergence can be tricky - functions may not live at the same address and may be different (however slightly). Maybe the basic machinery of advance/test/repeat could be parameterized to handle the easier scenarios and leave it at that. Such a script feels like more of a contrib-like patch, than part of gdb proper, but it still feels like something gdb could/should provide. When it works, it's a real timesaver, and the basic infrastructure shouldn't be that hard to write in python (and if it is then we've found good places where python needs to be extended). -- 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.
next reply other threads:[~2011-09-20 21:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-20 21:49 dje at google dot com [this message] 2011-09-20 22:07 ` [Bug external/13207] " pedro at codesourcery dot com 2011-09-20 22:14 ` pedro at codesourcery dot com 2011-09-21 11:36 ` dje at google dot com
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=bug-13207-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).