Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Pierre Muller (IMAP)" <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix troubles with watchpoints in DJGPP
Date: Wed, 27 May 2009 19:25:00 -0000	[thread overview]
Message-ID: <83ab4ys5zy.fsf@gnu.org> (raw)
In-Reply-To: <001401c9de9f$928b9f80$b7a2de80$@u-strasbg.fr>

> 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?


  reply	other threads:[~2009-05-27 19:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  7:49 Pierre Muller (IMAP)
2009-05-27 19:25 ` Eli Zaretskii [this message]
2009-05-27 20:53   ` Pierre Muller
2009-05-28  8:21     ` Eli Zaretskii
2009-05-28  9:31       ` Pierre Muller
2009-05-28 13:27         ` Eli Zaretskii
2009-05-27 23:30 ` Pedro Alves
2009-05-28  8:08   ` Eli Zaretskii
2009-06-08 16:16   ` [RFA-v2] " Pierre Muller
2009-06-16 22:38     ` [PING][RFA-v2] " Pierre Muller
2009-06-16 22:59       ` Pedro Alves
2009-06-16 23:20         ` Pierre Muller
2009-06-16 23:46           ` Pedro Alves
2009-06-16 23:54             ` Pierre Muller
2009-06-17  0:05               ` Pedro Alves
2009-06-17  6:19                 ` Pierre Muller
2009-06-17 12:32             ` Joel Brobecker
2009-06-17 22:44               ` DJ Delorie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83ab4ys5zy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox