From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25523 invoked by alias); 23 Jan 2003 18:41:46 -0000 Mailing-List: contact insight-prs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-prs-owner@sources.redhat.com Received: (qmail 25506 invoked by uid 48); 23 Jan 2003 18:41:46 -0000 Date: Thu, 23 Jan 2003 18:41:00 -0000 Message-ID: <20030123184146.25505.qmail@sources.redhat.com> To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com, llewins@raytheon.com, nobody@sources.redhat.com From: kseitz@sources.redhat.com Reply-To: kseitz@sources.redhat.com, insight-prs@sources.redhat.com, kseitz@sources.redhat.com, llewins@raytheon.com, nobody@sources.redhat.com, insight-gnats@sources.redhat.com Subject: Re: insight/206: SEGV in Tcl_FindCommand X-SW-Source: 2003-q1/txt/msg00019.txt.bz2 List-Id: Synopsis: SEGV in Tcl_FindCommand Responsible-Changed-From-To: unassigned->kseitz Responsible-Changed-By: kseitz Responsible-Changed-When: Thu Jan 23 18:41:46 2003 Responsible-Changed-Why: Mine State-Changed-From-To: open->closed State-Changed-By: kseitz State-Changed-When: Thu Jan 23 18:41:46 2003 State-Changed-Why: This is really a bug in GDB, not insight. Try running this with command line gdb (on any platform), and it will exhibit similar behavior (crash or lock-up). I suggest running this example on GDB and posting a report to gdb@sources.redhat.com. Here's what you'll want to do: $ c++ -g main.cc -o main $ gdb -nx -q main [or insight -nw main] (gdb) break 170 (gdb) r (gdb) p *b This will reproduce the whole thing. http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=206