From: Stan Shebs <shebs@apple.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: hjl@lucon.org, kettenis@wins.uva.nl, gdb@sourceware.cygnus.com
Subject: Re: gdb doesn't work very well with dynamic linked binaries
Date: Tue, 05 Sep 2000 18:02:00 -0000 [thread overview]
Message-ID: <39B59772.F3E69072@apple.com> (raw)
In-Reply-To: <200009051035.GAA06054@indy.delorie.com>
Eli Zaretskii wrote:
>
> > Date: Mon, 4 Sep 2000 23:32:22 -0700
> > From: "H . J . Lu" <hjl@lucon.org>
> >
> > If you can generalize it for ia32, I will implement it for Linux/ia32.
>
> The code on go32-nat.c manipulates an array which represents the ia32
> debug registers, including the status and control registers. It
> leaves it to resume() and its subroutines on the target end to
> actually insert the watchpoints when the inferior is resumed and
> remove them when the inferior stops and control is passed to GDB.
>
> If this model suits most or all ia32 targets, pulling the code from
> go32-nat.c into a separate module (probably, as part of i386-nat.c)
> would be very easy for me. If not, I'd ask the relevant maintainers
> to tell what provisions should I make for other platforms to fit in.
>
> > If it won't be fixed in 5.1, I will follow your hints and implement a
> > Linux only solution when it happens to me again.
>
> 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? :-)
Stan
next prev parent reply other threads:[~2000-09-05 18:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000901192328.A28312@valinux.com>
[not found] ` <200009041047.LAA10659@phal.cygnus.co.uk>
2000-09-04 8:49 ` H . J . Lu
2000-09-04 10:52 ` Mark Kettenis
2000-09-04 11:11 ` Daniel Berlin
2000-09-04 11:22 ` Ulrich Drepper
[not found] ` <drepper@redhat.com>
2000-09-05 19:12 ` Kevin Buettner
2000-09-04 16:45 ` H . J . Lu
2000-09-04 22:49 ` Eli Zaretskii
2000-09-04 23:32 ` H . J . Lu
2000-09-05 3:36 ` Eli Zaretskii
2000-09-05 6:34 ` Mark Kettenis
2000-09-05 8:47 ` Eli Zaretskii
2000-09-05 17:06 ` Mark Kettenis
2000-09-05 22:52 ` Eli Zaretskii
2000-09-05 8:49 ` H . J . Lu
2000-09-05 18:23 ` Stan Shebs
2000-09-05 18:33 ` H . J . Lu
2000-09-05 22:54 ` Eli Zaretskii
2000-09-05 8:44 ` H . J . Lu
2000-09-05 18:02 ` Stan Shebs [this message]
2000-09-05 20:45 ` H . J . Lu
2000-09-05 22:55 ` Eli Zaretskii
2000-10-14 23:09 ` Andrew Cagney
2000-09-05 22:53 ` Eli Zaretskii
[not found] ` <3.0.6.32.20000906001339.00b0ae90@idefix.wisa.be>
2000-09-05 23:08 ` About unified debug register handling for i386 CPU Eli Zaretskii
2000-09-06 10:10 ` Chris Faylor
2000-09-06 3:54 gdb doesn't work very well with dynamic linked binaries James Cownie
2000-09-06 4:58 ` Mark Kettenis
2000-09-07 1:55 James Cownie
2000-09-07 3:09 ` Mark Kettenis
2000-09-07 8:02 ` Eli Zaretskii
2000-09-08 8:30 ` Mark Kettenis
2000-09-09 14:39 ` Peter.Schauer
2000-09-07 3:27 James Cownie
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=39B59772.F3E69072@apple.com \
--to=shebs@apple.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sourceware.cygnus.com \
--cc=hjl@lucon.org \
--cc=kettenis@wins.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).