public inbox for
help / color / mirror / Atom feed
Subject: insight/333: local variable window blank with stack window when debugging core dumps
Date: Tue, 02 Dec 2008 02:33:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         333
>Category:       insight
>Synopsis:       local variable window blank with stack window when debugging core dumps
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 02 02:33:01 UTC 2008
>Release:        unknown-1.0
Slackware 12.1, insight-6.8
When debugging core dumps. if open local variable windows pane and change the stack level in the stack window, then local variable windows will change to the respected context,
but it will change to blank in fraction of a second, thus makes local variable window unusable. However this behaviour is not observed when debugging a running program (instead of a core dump).

It seems that insight-6.7.1 also has the same problem.



                 reply	other threads:[~2008-12-02  2:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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