This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Fix for testsuite errors with gdbserver (remote)
- From: Pedro Alves <pedro at codesourcery dot com>
- To: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 21 Feb 2011 15:47:01 +0000
- Subject: Re: [RFA] Fix for testsuite errors with gdbserver (remote)
- References: <4D5C71F6.80208@vmware.com> <201102211150.04538.pedro@codesourcery.com> <00b601cbd1db$7173d250$545b76f0$@muller@ics-cnrs.unistra.fr>
On Monday 21 February 2011 15:24:33, Pierre Muller wrote:
> > 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?
Go ahead and put it in, thanks.
--
Pedro Alves