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: Eli Zaretskii <eliz at gnu dot org>
- To: "Pierre Muller (IMAP)" <muller at ics dot u-strasbg dot fr>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 27 May 2009 22:25:21 +0300
- Subject: Re: [RFA] Fix troubles with watchpoints in DJGPP
- References: <001401c9de9f$928b9f80$b7a2de80$@u-strasbg.fr>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: "Pierre Muller \(IMAP\)" <muller@ics.u-strasbg.fr>
> Date: Wed, 27 May 2009 09:48:49 +0200
>
>
> I also tried to use it but I have several problems,
> some are probably DJGPP specific
> (bad file descriptor errors when trying to restart
> a ./gdb executable at level 2, meaning inside another gdb
> itself being debugged by gdb).
Please give me some simple test program and a transcript of a GDB
session that reproduces this problem. I debug GDB with itself a lot,
and I never saw this.
Also, on what platform (OS and version) is that?
> After some debugging, I realized that
> DJGPP only calls insert_breakpoints ()
> that does call update_watchpoint with reparse set to one,
> after pushing go32 target,
> while with cygwin, the DLL loaded caused a
> reloading of all breakpoints and triggered a
> call to update_watchpoint with reparse = 1.
>
>
> This one line patch fixes the problem.
>
> Is this patch OK?
Thanks, but here, too, I would like a simple test program and a
transcript of a GDB session before and after the patch.
> PS-2) Eli,
> do you have anything that could help me debug the
> Bad file descriptor problems, like a library recording
> file opening/closing using the DJGPP file system extensions?
No, but you can put a breakpoint on the respective library functions,
couldn't you?