public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Insight List <insight@sourceware.cygnus.com>
Subject: Restoring breakpoint failed
Date: Thu, 23 Aug 2001 15:31:00 -0000	[thread overview]
Message-ID: <87ae0q8jhb.fsf@creche.redhat.com> (raw)

I saved a session that included a breakpoint with attached commands.
When restoring the session, I got the appended error.

I'm pretty sure I tested this functionality when I wrote it, but to be
honest it is so long ago that it is hard to be certain.  Did something
change in `gdb_cmd' to make multi-line commands no longer work?
If so, how can breakpoint command restoration work?

FWIW for me it is very important that sessions work well.
They are the only feature that reliably separates Insight from using
gdb in Emacs (variable display would be another one, but I've learned
not to use that due to its propensity to provoke gdb crashes).

Tom

Unexpected extra arguments following breakpoint number.

    while executing
"gdb_cmd "commands \$bpnum\n[join $commands \n]""
    (procedure "SESSION_recreate_bps" line 21)
    invoked from within
"SESSION_recreate_bps $values(breakpoints)"
    (procedure "session_load" line 33)
    invoked from within
"session_load /x1/egcs/build/gcc/jc1"
    invoked from within
".srcwin0.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m#file invoke active"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 [list $w invoke active]"
    (procedure "tkMenuInvoke" line 29)
    invoked from within
"tkMenuInvoke .srcwin0.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m.#srcwin0#srcwin#container#pane0#childsite#con#menubar#m#file 1"
    (command bound to event)errorCode is NONE

             reply	other threads:[~2001-08-23 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23 15:31 Tom Tromey [this message]
2001-08-23 16:23 ` Keith Seitz
2001-08-23 16:50   ` Tom Tromey
2001-08-23 16:56     ` Keith Seitz

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=87ae0q8jhb.fsf@creche.redhat.com \
    --to=tromey@redhat.com \
    --cc=insight@sourceware.cygnus.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: link
Be 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).