public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: llewins@raytheon.com To: insight-gnats@sources.redhat.com Subject: insight/203: Error caused by automatic insertion of breakpoints Date: Fri, 10 Jan 2003 21:53:00 -0000 [thread overview] Message-ID: <20030110214720.20357.qmail@sources.redhat.com> (raw) >Number: 203 >Category: insight >Synopsis: Error caused by automatic insertion of breakpoints >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jan 10 13:53:00 PST 2003 >Closed-Date: >Last-Modified: >Originator: Lloyd J. Lewins >Release: cvs Jan 9, 2003 >Organization: >Environment: cygwin >Description: Debugged main.cc using insight, set breakpoint. Exited insight and modified main.cc. On restarting insight I received the following error message: No line 126 in file "main1.cc". while executing "gdb_cmd $create" (procedure "_recreate_bps" line 6) invoked from within "_recreate_bps $values(breakpoints)" (procedure "Session::notice_file_change" line 43) invoked from within "Session::notice_file_change" (procedure "gdbtk_tcl_preloop" line 20) invoked from within "gdbtk_tcl_preloop" >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-01-10 21:53 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030110214720.20357.qmail@sources.redhat.com \ --to=llewins@raytheon.com \ --cc=insight-gnats@sources.redhat.com \ /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).