public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Paul Breed <Paul@Netburner.com>
Cc: insight@sources.redhat.com
Subject: Re: Insight Shutdown behavior
Date: Thu, 26 Sep 2002 15:43:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0209261541590.15345-100000@valrhona.uglyboxes.com> (raw)
In-Reply-To: <5.0.2.1.2.20020926154004.03470350@mail.netburner.com>

[moved to insight list]

On Thu, 26 Sep 2002, Paul Breed wrote:

> When debugging with Insight as a cross debugger
> under windows one has to shutdown so that
> you can rebuild the elf file you are debugging.
> (Otherwise you have a sharing violation)

What's your target? As I recall, this is not an Insight bug. I don't even 
think it's a gdb bug. I remember this came up a long time ago...

> This is not totally unreasonable, but the really anoying part is that
> insight can randomly decide to take 20 or 30 seconds to shutdown.

Mine certainly doesn't take this long, even on windows.

> Any suggestions on:
> 
> 1)Leaving Insight open, and closing the file being debugged
> so one can rebuild?

Umm... File->Close?

> 2)Figuring out what takes so long when Insight shuts down.

What release are you using? Type "gdb -v". Also when you run Insight, open 
a console window and type "tk info tclversion". What's the result?

If you want to debug it, I would try starting insight under gdb and 
setting a break in gdb_force_quit. This is the place where shutdown 
starts.

Keith


           reply	other threads:[~2002-09-26 22:43 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5.0.2.1.2.20020926154004.03470350@mail.netburner.com>]

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=Pine.LNX.4.44.0209261541590.15345-100000@valrhona.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=Paul@Netburner.com \
    --cc=insight@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).