This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Fix troubles with watchpoints in DJGPP
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: "Pierre Muller \(IMAP\)" <muller at ics dot u-strasbg dot fr>, "'Eli Zaretskii'" <eliz at gnu dot org>
- Date: Thu, 28 May 2009 00:30:28 +0100
- Subject: Re: [RFA] Fix troubles with watchpoints in DJGPP
- References: <001401c9de9f$928b9f80$b7a2de80$@u-strasbg.fr>
On Wednesday 27 May 2009 08:48:49, Pierre Muller (IMAP) wrote:
> PS-1) Are there not other native targets, without
> dynamic libraries, that will suffer the same troubles?
I think so. I've just tried on x86_64-linux, with a statically
linked binary (I used gdb.threads/staticthreads, set a watchpoint
on semaphore), and although there are no shared libraries loaded,
the problem is masked by adding the symbols of the vsyscall page
(sysfile-mem.c:add_vsyscall_page). If I hack that function to
do nothing, I see that same thing you're seeing on djgpp.
Maybe there's a place for a generic fix? Somewhere after
having opened a connection to the target interface. I was
thinking of post_create_inferior, but sounds like opening
a connection to a remote target with "target remote" that
happens to not pull in any more symbols (like most embedded
targets) is having the same problem? Maybe there should be
a target_post_open ...
--
Pedro Alves