Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Keith Seitz <keiths@redhat.com>,
	       Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Subject: Re: [RFA] Fix for testsuite errors with gdbserver (remote)
Date: Fri, 18 Feb 2011 20:30:00 -0000	[thread overview]
Message-ID: <m3d3mpxf6q.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201102181954.25496.pedro@codesourcery.com> (Pedro Alves's	message of "Fri, 18 Feb 2011 19:54:25 +0000")

>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:

Pedro> I'm not convinced.  It looks like a workaround for something
Pedro> the python exited observer isn't doing right.

That could be, but what is that?

All that python_inferior_exit is doing to provoke the crash is calling
get_current_arch.  Under what circumstances is this not safe?  I would
have thought -- perhaps naively -- that it was always safe.

Tom


  reply	other threads:[~2011-02-18 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D5C71F6.80208@vmware.com>
     [not found] ` <4D5C7552.4010708@vmware.com>
     [not found]   ` <4D5C8312.4030701@vmware.com>
     [not found]     ` <4D5D6D83.8030302@vmware.com>
     [not found]       ` <4D5D8974.5030205@redhat.com>
2011-02-18 16:50         ` Pierre Muller
2011-02-18 18:56           ` Keith Seitz
2011-02-18 20:26             ` Pedro Alves
2011-02-18 20:30               ` Tom Tromey [this message]
2011-02-18 20:31                 ` Tom Tromey
2011-02-21 11:50                   ` Pedro Alves
2011-02-21 15:47                     ` Pierre Muller
2011-02-21 15:54                       ` Pedro Alves

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=m3d3mpxf6q.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=pedro@codesourcery.com \
    --cc=pierre.muller@ics-cnrs.unistra.fr \
    /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