From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>
Subject: Re: RFC: fix PR mi/10693
Date: Mon, 10 Jan 2011 23:48:00 -0000 [thread overview]
Message-ID: <201101102348.04761.pedro@codesourcery.com> (raw)
In-Reply-To: <m3oc7oldow.fsf@fleche.redhat.com>
On Monday 10 January 2011 20:13:35, Tom Tromey wrote:
> I would appreciate comments on this.
- What about info_sharedlibrary_command's update_solib_list call?
- I haven't really checked, but do we now need to care about
exceptions between reading the shared library, and
calling the observer leaving the frontend out of sync?
(e.g., quits, or some other error thrown while reading debug
info or printing something).
--
Pedro Alves
next prev parent reply other threads:[~2011-01-10 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 20:13 Tom Tromey
2011-01-10 23:48 ` Pedro Alves [this message]
2011-02-04 16:15 ` Tom Tromey
2011-02-04 17:03 ` Tom Tromey
2011-02-04 18:19 ` Eli Zaretskii
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=201101102348.04761.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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