Bug 16785 - internal error with "target record-full" followed by "checkpoint"
Summary: internal error with "target record-full" followed by "checkpoint"
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: HEAD
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-31 14:40 UTC by patrick
Modified: 2015-09-15 12:25 UTC (History)
2 users (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 patrick 2014-03-31 14:40:43 UTC 
To reproduce:

$ gdb gdb
break main
run
target record-full
checkpoint

This sequence of commands results in the error "record_full_remove_breakpoint: removing unknown breakpoint".

I can reproduce this error on gdb 7.6.2 and 7.7.50.20140331.
Comment 1 OmegaPhil 2014-09-16 16:46:54 UTC 
I get something similar to this with the following command:

====================================================================

gdb -ex "start --fork --replace --tab -n \"Bash 1 - %s\"" -ex "set follow-fork-mode child" -ex record -ex continue /mnt/Storage_1/Programming/C/roxterm/roxterm/build/roxterm

====================================================================

gdb runs, then a few seconds later I get the following:

====================================================================

/home/zumbi/gdb-7.7.1+dfsg/gdb/record-full.c:1818: internal-error: record_full_remove_breakpoint: removing unknown breakpoint
A problem internal to GDB has been detected,
further debugging may prove unreliable.

====================================================================

When I remove the parameters passed to start, gdb appears to work - I get 'Do you want to auto delete previous execution log entries when record/replay buffer becomes full (record full stop-at-limit)?' - agreeing allows gdb to continue.
Comment 2 Michael Fiedler 2015-09-15 12:25:12 UTC 
I can reproduce this bug using the commands in the initial description and gdb 7.10.50.20150915-cvs (current HEAD ade90bdeb78ccaeb294e34af04751f2f649a324f) on Ubuntu 14.04 x86_64.