Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] Fix for testsuite errors with gdbserver (remote)
Date: Mon, 21 Feb 2011 15:47:00 -0000	[thread overview]
Message-ID: <00b601cbd1db$7173d250$545b76f0$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <201102211150.04538.pedro@codesourcery.com>

> That all said, it looks like the python api doesn't define
> exactly what can be done on an ExitedEvent, and even if
> we address the gdbarch issue, if it's intended that the
> python user code can do whatever, we're likely to see python/gdb
> calls there that try to do something that calls has_stack_frames,
> and that will internal error too.  On that ground, I do think
> we should put in Pierre's patch, as I'm not seeing what
> possible harm can it do, and that gets things working again.
> But I'll note that if the handler is allowed to assume the
> whole api is available at this point, and that the current
> global state can be used as if in the top-level, we'll
> probably see other similar cases triggering.


  Should I take this as an approval of my patch?
Or do you want me to wait some more in case someone
else has a better idea of how to fix this issue?

Pierre


  reply	other threads:[~2011-02-21 15:24 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
2011-02-18 20:31                 ` Tom Tromey
2011-02-21 11:50                   ` Pedro Alves
2011-02-21 15:47                     ` Pierre Muller [this message]
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='00b601cbd1db$7173d250$545b76f0$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --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