This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: how to continue from a breakpoint in GNU/Hurd
- From: Yue Lu <hacklu dot newborn at gmail dot com>
- To: Richard Braun <rbraun at sceen dot net>
- Cc: Luis Machado <lgustavo at codesourcery dot com>, gdb at sourceware dot org, bug-hurd at gnu dot org, Thomas Schwinge <thomas at codesourcery dot com>
- Date: Thu, 18 Jul 2013 00:07:20 +0800
- Subject: Re: how to continue from a breakpoint in GNU/Hurd
- References: <CAB8fV=i04n-eHTxP=7hWRkB7O1VJobvrMc5KSHOX0SkJ3vuqhQ at mail dot gmail dot com> <51E5785D dot 1050904 at codesourcery dot com> <CAB8fV=iuUFiNtoU-Trw_GnujMW1REMj2=ZciR=36RDJx1+8wSQ at mail dot gmail dot com> <51E58223 dot 5040505 at codesourcery dot com> <CAB8fV=jnOcYCGmQ_emcoE0ZYH6MjT3K3a1P8=svRR+nKSMD69A at mail dot gmail dot com> <20130717120954 dot GA26158 at dalaran dot sceen dot net>
Hi.
On Wed, Jul 17, 2013 at 8:09 PM, Richard Braun <rbraun@sceen.net> wrote:
> On Wed, Jul 17, 2013 at 02:11:58PM +0800, Yue Lu wrote:
>> When I get the exception message, I set the EIP to the next instruction
>> (for instance 0x12345678), after resume it, I call get_thread_state(), and
>> found the EIP is still 0x12345678. The inferior never running anymore.
>
> I don't think it has anything to do with the instruction cache. Use the
> thread_info() call to determine what the suspend count is, it may have
> been incremented implicitely.
when I used thread_info() to check the suspend count, they are zero.
But I met a strange thing.
this is my code snippet:
thread_basic_info_data_t _info;
thread_basic_info_t info = &_info;
mach_msg_type_number_t info_len = THREAD_BASIC_INFO_COUNT;
error_t err =
thread_info (thread->port, THREAD_BASIC_INFO, (int *) &info, &info_len);
after this call, the info turn out to be a _NULL_ pointer. I think
something maybe wrong, but the err is zero.
In thread_takeover_sc_cmd() [gdb/gdb/gnu-nat.c] it has directly access
info after thread_info call, so I think this pointer never become a
NULL pointer, but in my code, it does. So I think something maybe
wrong, or this is a bug in gdb code.
--
Yue Lu (éå)