public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "OmegaPhil at startmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16785] internal error with "target record-full" followed by "checkpoint" Date: Tue, 16 Sep 2014 16:46:00 -0000 [thread overview] Message-ID: <bug-16785-4717-POafjPAK19@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16785-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16785 OmegaPhil at startmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |OmegaPhil at startmail dot com --- Comment #1 from OmegaPhil at startmail dot com --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
next parent reply other threads:[~2014-09-16 16:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-16785-4717@http.sourceware.org/bugzilla/> 2014-09-16 16:46 ` OmegaPhil at startmail dot com [this message] 2015-09-15 12:25 ` dev@michael-fiedler.net
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-16785-4717-POafjPAK19@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).