This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] More suggestive displaced-stepping memory error message

From: Yao Qi <yao at codesourcery dot com>
To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
Cc: <gdb-patches at sourceware dot org>
Date: Wed, 11 Apr 2012 16:53:09 +0800
Subject: Re: [patch] More suggestive displaced-stepping memory error message
References: <20120410191955.GB31331@host2.jankratochvil.net> <4F84C2D7.1070203@codesourcery.com> <20120411084104.GA21919@host2.jankratochvil.net>

On 04/11/2012 04:41 PM, Jan Kratochvil wrote:
>> > So far,
>> > displaced_step_prepare returns 1 for success and 0 for queued request.
>> > We can add one more return value -1 for `unable to do displaced
>> > stepping', so that caller can go non-displaced-stepping path.
> We could discuss first more the cases when it can happen and it is not some
> GDB bug.  So far I know only about the ld.so initialization.
> 
> As I see there are concerns about the message I will just check in this part,
> it should be sufficient for troubleshooting.

Looks like it is a corner case, and throwing an error message is fine to me.

-- 
Yao (éå)

References:
- [patch] More suggestive displaced-stepping memory error message
  - From: Jan Kratochvil
- Re: [patch] More suggestive displaced-stepping memory error message
  - From: Yao Qi
- Re: [patch] More suggestive displaced-stepping memory error message
  - From: Jan Kratochvil

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]