This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Unclear error message from gdbserver
- From: Daniel Jacobowitz <drow at false dot org>
- To: Hans Zuidam <h dot zuidam at computer dot org>
- Cc: gdb at sourceware dot org
- Date: Tue, 20 Feb 2007 20:53:19 -0500
- Subject: Re: Unclear error message from gdbserver
- References: <400B4AB8-3CE3-44B8-A4AF-A3F1037CFADC@wanadoo.nl>
On Wed, Feb 21, 2007 at 12:15:13AM +0100, Hans Zuidam wrote:
> Hi,
>
> When running a (large) multi-threaded application on a MIPS target I
> get a warning
> from gdbserver:
>
> Hit a removed breakpoint?
>
> (in mem-break.c:check_breakpoints)
>
> Specifically, the warning is issued during thread creation. No
> breakpoints were set,
> just gdb's internal breakpoints and the application was started with
> `r'un.
>
> More specifically I do not quite understand the meaning of the
> `reinserting' member
> in the breakpoint structure and how it could get set for internal
> breakpoints.
>
> Could it be a bug in the specific gdbserver implementation (not a
> stock gdb 6.4 one?)
Yes, it's quite likely. GDB supports MIPS GNU/Linux, and this is for
the Linux-specific threading support, so I don't know why you need a
customized gdbserver.
If NPTL is involved, it could also be this:
http://sourceware.org/bugzilla/show_bug.cgi?id=2697
The reinserting member is used to bypass a breakpoint, after it is
hit. A temporary breakpoint is inserted nearby, the thread is
advanced past its former location, and then the original breakpoint is
reinserted.
--
Daniel Jacobowitz
CodeSourcery