Bug 12924 - Update breakpoint locations more precisely when program is re-run on different address
Summary: Update breakpoint locations more precisely when program is re-run on differen...
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: breakpoints (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-23 13:46 UTC by Yao Qi
Modified: 2011-06-23 14:17 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yao Qi 2011-06-23 13:46:57 UTC 
On some systems, such uclinux, program may be run on the different addresses from time to time.  Current GDB is unable to update breakpoint locations when program is re-run on different address.  Some state in breakpoint location is lost during re-running new program.

Some discussions can be found in this thread http://sourceware.org/ml/gdb-patches/2011-06/msg00335.html
Comment 1 Pedro Alves 2011-06-23 14:17:11 UTC 
Specifically, GDB is able to recreate the locations, but is unable to match new locations with old locations, and so state such as which locations were disabled is lost.