From: Keith Seitz <kseitz@firetalk.com>
To: Mo DeJong <mdejong@cygnus.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Insight crash I have not seen before.
Date: Thu, 27 Apr 2000 05:38:00 -0000 [thread overview]
Message-ID: <390834C3.88E681EB@firetalk.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10004270132120.31781-100000@abomination.cygnus.com>
Mo DeJong wrote:
>
> Nevermind the last email I sent with the stack trace. I got this
> crash a couple of times and gdb never seems to core in the same
> place twice. I think the problem is actually with gdb rereading
> symbols from and applicaiton when you recompile tha app in between
> runs in the debugger (without quitting the debugger). My app
> was also dying from a call to assert(), but I am not sure if
> that made a diff.
>
> I was running on Red Hat 6.2 when I got these crashes by the way.
This came up last week with Tom. Fernando has some state on it. What's
happening is that the variable code that gdbtk uses (which I guess gdb
is going to slowly migrate to?) hangs on to a lot of pointers to the
symbol table and obstacks. When the symbol table is re-read (and maybe
even if you just re-run the executable), all of these references are
bogus.
We found out that a hook which is supposed to clean this up is not being
run anymore. I think this is either the clear_file or no_inferior hook.
Both the variable windows (Locals and Watch) and the SrcTextWin
(variable balloons) should be erasing any variable objects whenever the
inferior is killed/re-run or has symbols re-read.
Keith
--
Why chat when you can Firetalk?
Firetalk ID: Keith (10320)
www.firetalk.com
next prev parent reply other threads:[~2000-04-27 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-27 0:17 Mo DeJong
2000-04-27 1:35 ` Mo DeJong
2000-04-27 5:38 ` Keith Seitz [this message]
2000-04-27 9:08 ` Fernando Nasser
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=390834C3.88E681EB@firetalk.com \
--to=kseitz@firetalk.com \
--cc=insight@sourceware.cygnus.com \
--cc=mdejong@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).