Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] Error reporting during insert_breakpoints
Date: Fri, 23 Oct 2009 15:36:00 -0000	[thread overview]
Message-ID: <4AE1CBCC.3010706@vmware.com> (raw)
In-Reply-To: <200906032246.44508.pedro@codesourcery.com>

Pedro Alves wrote:
> On Wednesday 03 June 2009 21:42:14, Michael Snyder wrote:
>> Two small changes
>>
>> 1) If insert_breakpoints fails during stepping, "keep_going()"
>> contains a TRY_CATCH block, but does not print the exception error.
>> If the same thing happens during continue, "catch_errors" reports it.
> 
> Yes, please.  This silent stop bites me often, when longjmp-resume
> breakpoints fail to insert due to glibc pointer mangling...

Fell through the cracks, checking in now.



      parent reply	other threads:[~2009-10-23 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 20:45 Michael Snyder
2009-06-03 21:46 ` Pedro Alves
2009-06-03 22:10   ` Pedro Alves
2009-10-23 15:36   ` Michael Snyder [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=4AE1CBCC.3010706@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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