public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Gene Smith <gds@chartertn.net>
Cc: insight@sources.redhat.com
Subject: Re: Two small insight (gdb?) bugs
Date: Mon, 01 Aug 2011 22:32:00 -0000	[thread overview]
Message-ID: <4E372962.1020303@redhat.com> (raw)
In-Reply-To: <j0ioam$nav$1@dough.gmane.org>

On 07/24/2011 08:35 PM, Gene Smith wrote:
> Keith Seitz wrote, On 07/24/2011 02:45 PM:
>> On 07/12/2011 09:32 PM, Gene Smith wrote:
>>> 1. In console I can set a breakpoint like this:
>>>
>>> b main
>>>
>>> But if I make a typo and enter an invalid symbol such as:
>>>
>>> b mai
>>>
>>> It hangs insight and I have to kill -9 it.

Since I cannot reproduce this, is there any chance you can attach a 
debugger to this running instance and get me a backtrace?

> Clicking on "Details>>" I see this:
> invalid command name "var6"
> invalid command name "var6"
> while executing
> "$var delete"
> while deleting object "::.watchwin0.watchwin" in ::WatchWin::destructor
> (body line 11)
> invoked from within
> "itcl::delete object ::.watchwin0.watchwin"
> (command bound to event)

The varobjs are destroyed by the callback, but when the window is closed 
and the dtor is called, it tried to delete the varobjs again because the 
callback did not clear the list. This should be fixed by my patch.

> Also, it might be considered a bug in that the watchpoints are not
> remembered between insight restarts or after a reload of flash, at least
> for me. (At least BPs are remembered which is handy.)

I don't know why they were omitted. Maybe it is a little trickier than 
breakpoints because of possible context restrictions. I might be able to 
work up a patch for this.

Keith

      reply	other threads:[~2011-08-01 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13  4:32 Gene Smith
2011-07-24 18:46 ` Keith Seitz
2011-07-24 19:32   ` Keith Seitz
2011-07-25  3:36   ` Gene Smith
2011-08-01 22:32     ` Keith Seitz [this message]

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=4E372962.1020303@redhat.com \
    --to=keiths@redhat.com \
    --cc=gds@chartertn.net \
    --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).