public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: "Lloyd J Lewins" <llewins@raytheon.com>
To: kseitz@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: Re: insight/206: SEGV in Tcl_FindCommand
Date: Fri, 24 Jan 2003 01:23:00 -0000 [thread overview]
Message-ID: <20030124012301.17699.qmail@sources.redhat.com> (raw)
The following reply was made to PR insight/206; it has been noted by GNATS.
From: "Lloyd J Lewins" <llewins@raytheon.com>
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
Cc:
Subject: Re: insight/206: SEGV in Tcl_FindCommand
Date: Thu, 23 Jan 2003 17:15:55 -0800
Running the same version of insight with -nw as you suggest (on cygwin
platform) I do not see the problem:
~/bugs/gdb/Tcl-FindCommand-SEGV>insight -nw main.exe
GNU gdb 2003-01-09-cvs
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) b 170
Breakpoint 1 at 0x401280: file main.cc, line 170.
(gdb) r
Starting program: /home/00c3197/bugs/gdb/Tcl-FindCommand-SEGV/main.exe
Breakpoint 1, main () at main.cc:170
170 }
(gdb) p *b
$1 = {<classC> = {nameV = {static npos = 4294967295, static nilRep = {len
= 0,
res = 0, ref = 2, selfish = false}, dat = 0xa012378 "foo"},
myClassAV = @0xa0b3780}, _vb$classC = 0xa011af8, valV = 0,
_vptr$classB = 0x4156bc <classB virtual table>}
(gdb)
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.
Lloyd J. Lewins
Raytheon Co.,
llewins@raytheon.com
+1 (310) 647-8832
kseitz@sources.r
edhat.com To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com, llewins@raytheon.com,
nobody@sources.redhat.com
01/23/03 10:41 cc:
AM Subject: Re: insight/206: SEGV in Tcl_FindCommand
Please respond
to kseitz;
Please respond
to insight-prs;
Please respond
to kseitz;
Please respond
to llewins;
Please respond
to nobody;
Please respond
to insight-gnats
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
next reply other threads:[~2003-01-24 1:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 1:23 Lloyd J Lewins [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-24 13:43 Keith Seitz
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:
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=20030124012301.17699.qmail@sources.redhat.com \
--to=llewins@raytheon.com \
--cc=insight-prs@sources.redhat.com \
--cc=kseitz@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: 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).