This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb doesn't work very well with dynamic linked binaries
- To: "H . J . Lu" <hjl at lucon dot org>
- Subject: Re: gdb doesn't work very well with dynamic linked binaries
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Wed, 11 Oct 2000 01:50:15 -0400
- Cc: Stan Shebs <shebs at apple dot com>, Eli Zaretskii <eliz at is dot elta dot co dot il>,kettenis at wins dot uva dot nl, gdb at sourceware dot cygnus dot com
- References: <20000901192328.A28312@valinux.com> <200009041047.LAA10659@phal.cygnus.co.uk> <20000904084934.A11100@lucon.org> <200009041751.e84HprD11517@debye.wins.uva.nl> <20000904164458.A12270@lucon.org> <200009050548.BAA05890@indy.delorie.com> <200009042 <20000905204519.A18325@lucon.org>
FYI,
I'm going to apply this patch but as part of the 5.2 criteria. If it is
fixed in 5.1 then it is a bonus.
enjoy,
Andrew
"H . J . Lu" wrote:
>
> On Tue, Sep 05, 2000 at 06:01:39PM -0700, Stan Shebs wrote:
> > >
> > > I can do this Very Soon (tm) provided that I hear a GO from The Powers
> > > That Be. Andrew? Stan? What say you?
> >
> > Uh, is there any reason not to? We tell people that GDB can support
> > h/w watchpoints, seems like we ought to deliver it on our most popular
> > platforms. Perhaps I could be evil and insist on adding a testsuite test
> > that would take 24 hours to run if h/w watchpoints don't work... think
> > that would help motivate anyone? :-)
> >
>
> How about this patch? As I said, I will work on Linux since I use this
> feature a lot.
>
> Thanks.
>
> H.J.
> ----
> 2000-09-05 H.J. Lu <hjl@gnu.org>
>
> * TODO: Add hardware watchpint problems on x86 OSes for 5.1.
>
> --- TODO Thu Aug 10 15:23:13 2000
> +++ /tmp/TODO Tue Sep 5 20:41:08 2000
> @@ -12,6 +12,26 @@ cycle. People hope to have these proble
>
> --
>
> +Hardware watchpint problems on x86 OSes, including Linux:
> +
> +1. Delete/disable hardware watchpoints should free hardware debug
> +registers.
> +2. Watch for different values on a viariable with one hardware debug
> +register.
> +
> +According to Eli Zaretskii <eliz@delorie.com>:
> +
> +These are not GDB/ia32 issues per se: the above features are all
> +implemented in the DJGPP port of GDB and work in v5.0. Every
> +x86-based target should be able to lift the relevant parts of
> +go32-nat.c and use them almost verbatim. You get debug register
> +sharing through reference counts, and the ability to watch large
> +regions (up to 16 bytes) using multiple registers. (The required
> +infrastructure in high-level GDB application code, mostly in
> +breakpoint.c, is also working since v5.0.)
> +
> +--
> +
> RFD: infrun.c: No bpstat_stop_status call after proceed over break?
> http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html
>