From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>,
Mark Kettenis <kettenis@science.uva.nl>
Cc: gdb-patches@sources.redhat.com
Subject: [RFC] Possible bug with i386 watchpoints on several targets.
Date: Wed, 21 Nov 2001 17:07:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20011130165213.016940c0@ics.u-strasbg.fr> (raw)
In-Reply-To: <5567-Fri30Nov2001174510+0200-eliz@is.elta.co.il>
At 16:45 30/11/2001 , Eli Zaretskii a écrit:
> > Date: Fri, 30 Nov 2001 16:17:27 +0100
> > From: Pierre Muller <muller@cerbere.u-strasbg.fr>
> >
> > What do we do about this?
> > I proposed to add a call to i386_cleanup_dregs
> > for all targets using the standard
> > i386 hardware watchpoints, but
> > Eli seems still not convinced by my reports....
>
>You don't need to convince me (the port I'm responsible for _does_
>use i386_cleanup_dregs, after all ;-). You need to convince Mark
>Kettenis. I'm sure that if you post a test program and a full recipe
>to reproduce the problem, and then show the patch which makes the
>problem go away, Mark will happily accept it.
The way to check if the bug exist is easy:
take gdb (5.1 or current snapshot)
compiled with debug info and
run
./gdb ./gdb
on the newly generated executable.
(preferabily in the compilation dir,
which will ensure that you get (top-gdb) prompt
for the debugger and (gdb) for the debuggee).
use the following command
(top-gdb) watch gdb_stdout
(top-gdb) r
Here you should get a stop due to the setting of gdb_stdout value.
(top-gdb) cont
you should now reach the debuggee command prompt,
simply quit.
(gdb) quit
and rerun the same executable without any watchpoint modification.
(top-gdb) run
if the bug that I found on both win32 (without i386_cleanup_deregs call)
and on current (a few days old) CVS for linux.
You won't get any stop on the second run.
The fix is not that obvious, because I am still a bit unclear
about wher it should be put:
the i386_cleanup_dregs should be called (in my opinion)
both when a program is killed and when a program
terminates normally.
But linux does seem to use generic_mourn_inferior,
so for this target it would probably require that we
change this into a target specific function.
PS: Eli, did you check the go32v2 target if you kill the program after
the watchpoint is reached, sorry, I still can't get GDB to compile for djgpp
on my win2000.
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
WARNING: multiple messages have this Message-ID
From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>,
Mark Kettenis <kettenis@science.uva.nl>
Cc: gdb-patches@sources.redhat.com
Subject: [RFC] Possible bug with i386 watchpoints on several targets.
Date: Fri, 30 Nov 2001 08:06:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20011130165213.016940c0@ics.u-strasbg.fr> (raw)
Message-ID: <20011130080600.8-NHLRJEWPpy2FYb2E0LVgmhy5ZJVWZpjewdRSH_E08@z> (raw)
In-Reply-To: <5567-Fri30Nov2001174510+0200-eliz@is.elta.co.il>
At 16:45 30/11/2001 , Eli Zaretskii a écrit:
> > Date: Fri, 30 Nov 2001 16:17:27 +0100
> > From: Pierre Muller <muller@cerbere.u-strasbg.fr>
> >
> > What do we do about this?
> > I proposed to add a call to i386_cleanup_dregs
> > for all targets using the standard
> > i386 hardware watchpoints, but
> > Eli seems still not convinced by my reports....
>
>You don't need to convince me (the port I'm responsible for _does_
>use i386_cleanup_dregs, after all ;-). You need to convince Mark
>Kettenis. I'm sure that if you post a test program and a full recipe
>to reproduce the problem, and then show the patch which makes the
>problem go away, Mark will happily accept it.
The way to check if the bug exist is easy:
take gdb (5.1 or current snapshot)
compiled with debug info and
run
./gdb ./gdb
on the newly generated executable.
(preferabily in the compilation dir,
which will ensure that you get (top-gdb) prompt
for the debugger and (gdb) for the debuggee).
use the following command
(top-gdb) watch gdb_stdout
(top-gdb) r
Here you should get a stop due to the setting of gdb_stdout value.
(top-gdb) cont
you should now reach the debuggee command prompt,
simply quit.
(gdb) quit
and rerun the same executable without any watchpoint modification.
(top-gdb) run
if the bug that I found on both win32 (without i386_cleanup_deregs call)
and on current (a few days old) CVS for linux.
You won't get any stop on the second run.
The fix is not that obvious, because I am still a bit unclear
about wher it should be put:
the i386_cleanup_dregs should be called (in my opinion)
both when a program is killed and when a program
terminates normally.
But linux does seem to use generic_mourn_inferior,
so for this target it would probably require that we
change this into a target specific function.
PS: Eli, did you check the go32v2 target if you kill the program after
the watchpoint is reached, sorry, I still can't get GDB to compile for djgpp
on my win2000.
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2001-11-30 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4.2.0.58.20011121124943.00a4a288@ics.u-strasbg.fr>
[not found] ` <1190-Wed21Nov2001202555+0200-eliz@is.elta.co.il>
2001-11-30 7:18 ` Bug with watchpoints on Linux Pierre Muller
2001-11-21 16:19 ` Pierre Muller
2001-11-21 16:50 ` Eli Zaretskii
2001-11-21 17:07 ` Pierre Muller [this message]
2001-11-30 8:06 ` [RFC] Possible bug with i386 watchpoints on several targets Pierre Muller
2001-11-30 11:48 ` Eli Zaretskii
2001-11-23 6:39 ` Eli Zaretskii
2001-12-03 1:33 ` Pierre Muller
2001-12-03 3:10 ` Eli Zaretskii
2001-12-04 4:09 ` Pierre Muller
2001-12-04 23:50 ` Eli Zaretskii
2001-12-05 1:31 ` Pierre Muller
2001-12-05 3:23 ` Eli Zaretskii
2001-12-05 3:55 ` Pierre Muller
2001-11-30 7:45 ` Bug with watchpoints on Linux Eli Zaretskii
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=4.2.0.58.20011130165213.016940c0@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@science.uva.nl \
/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