public inbox for
help / color / mirror / Atom feed
Subject: Re: insight/347: Application crashen when hex value in watch not prefixed
Date: Thu, 29 Apr 2010 20:32:00 -0000	[thread overview]
Message-ID: <> (raw)

Synopsis: Application crashen when hex value in watch not prefixed

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Thu Apr 29 20:32:35 2010
State-Changed-From-To: open->analyzed
State-Changed-By: kseitz
State-Changed-When: Thu Apr 29 20:32:35 2010
    Something changed in varobj.c: there is a call to parse_exp_1 which is not caught or surrounded by TRY/CATCH. I can only assume that input is required to be validated by the UI -- a significant change from previous incantations of this API.
    Working on a patch...

             reply	other threads:[~2010-04-29 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 20:32 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-29 21:02 kseitz
2009-11-23 15:03 lwierzbi

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