Call target_close after unpushing, not before

Pedro Alves palves@redhat.com
Thu Jan 19 16:37:00 GMT 2012

Previous message (by thread): Call target_close after unpushing, not before (was: Re: [patch] Fix remote.c crash on gdbserver close (+fix py-finish-breakpoint.exp for gdbserver))
Next message (by thread): [commit] Re: Call target_close after unpushing, not before (was: Re: [patch] Fix remote.c crash on gdbserver close (+fix py-finish-breakpoint.exp for gdbserver))
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 01/19/2012 04:23 PM, Jan Kratochvil wrote:
> On Thu, 19 Jan 2012 17:02:31 +0100, Pedro Alves wrote:
>> Any comments on this?
> 
> I am fine with it with the comment update.

Good idea.  Please go ahead.  I've applied my patch.

Thanks,
-- 
Pedro Alves

Previous message (by thread): Call target_close after unpushing, not before (was: Re: [patch] Fix remote.c crash on gdbserver close (+fix py-finish-breakpoint.exp for gdbserver))
Next message (by thread): [commit] Re: Call target_close after unpushing, not before (was: Re: [patch] Fix remote.c crash on gdbserver close (+fix py-finish-breakpoint.exp for gdbserver))
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Gdb-patches mailing list