public inbox for
help / color / mirror / Atom feed
From: Keith Seitz <>
Subject: Re: insight/206: SEGV in Tcl_FindCommand
Date: Fri, 24 Jan 2003 13:43:00 -0000	[thread overview]
Message-ID: <> (raw)

The following reply was made to PR insight/206; it has been noted by GNATS.

From: Keith Seitz <>
To: Lloyd J Lewins <>
Subject: Re: insight/206: SEGV in Tcl_FindCommand
Date: 24 Jan 2003 05:36:29 -0800

 On Thu, 2003-01-23 at 17:15, Lloyd J Lewins wrote:
 > Running the same version of insight with -nw as you suggest (on cygwin
 > platform) I do not see the problem:
 Hmmm. That is odd. My gdb (cvs head) locks up on me when I ask it to do
 > Since the SEGV is in tcl functions, I am surprised this is a problem with
 > gdb -- I thought it was only insight which used tcl/tk.
 Typically, insight will not crash in a platform-specific way. You're
 using c++ and there has been a lot of churn in gdb (and its
 dependencies) in this area.
 You're using the standard cygwin compiler,, right? I'm using
 3.2. Maybe that's why. In any case I don't think that Insight is really
 crashing in tcl/tk. I think that the stack has been corrupted.
 Let's try this... Run your program (in insight) to where you would add
 it to the watch window. Then open a console window and enter:
 (gdb) tk gdb_variable create -expr b
 var1 (<-- could be different object id)
 (gdb) tk var1 numChildren
 (gdb) tk var1 children
 What's the output? Do either of these cause a crash? If they do, try the
 same thing in MI:
 $ gdb -i=mi main
 break 170
 -var-create - * b
 ^done,name="var1",numchild="2",type="classB *"
 -var-list-children var1
 What does this show? I'll see about updating my cygwin box (er, that
 means actually turning it on, which I haven't done in a very long time),
 but it's going to take quite some time. Please ping me on this if you
 don't hear from me for a week.

             reply	other threads:[~2003-01-24 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 13:43 Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-24  1:23 Lloyd J Lewins
2003-01-23 18:41 kseitz
2003-01-21  0:53 llewins

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).