Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: James Cownie <jcownie@etnus.com>
To: gdb@sources.redhat.com
Subject: Re: gdb doesn't work very well with dynamic linked binaries
Date: Wed, 06 Sep 2000 03:54:00 -0000	[thread overview]
Message-ID: <200009061054.GAA28894@albacore> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2606 bytes --]

This threads seems really to have morphed to be about using the
hardware watchpoint registers on IA32.

So :-

Note that there are a couple of linux kernel bugs in 2.2 (one of which
was fixed in 2.2.17) which affect the use of the debug registers.

The first bug (which was fixed in 2.2.17) was that the debug status
register wasn't being saved where it could be seen by ptrace, so if
you were relying on looking at the hardware status register you were
stuffed.

The second (which isn't yet fixed) I described with a test case in a
previous mail here. ( http://sources.redhat.com/ml/gdb/2000-08/msg00072.html )
Basically the kernel ignores all hardware
watchpoints from the point where one of them is triggered inside the
kernel until a reschedule. This means many watchpoints at user level
can be silently skipped :-(

AFAICS both bugs remain in 2.4.0-test7.

-- Jim 

James Cownie	<jcownie@etnus.com>
Etnus, LLC.     +44 117 9071438
http://www.etnus.com



-- 
-- Jim
James Cownie
jcownie@etnus.com
Etnus, Inc.
Phone +44 117 9071438
From mdeans@algonet.se Wed Sep 06 04:13:00 2000
From: "Bjorn Eriksson" <mdeans@algonet.se>
To: "Russ.Shaw" <russell@webaxs.net>, "Michael Sokolov" <msokolov@ivan.Harhan.ORG>
Cc: <binutils@sources.redhat.com>, <crossgcc@sources.redhat.com>, <gcc@gcc.gnu.org>, <gdb@sources.redhat.com>
Subject: comp.gnu.embedded (was: embedded An article about the Cygnus tree)
Date: Wed, 06 Sep 2000 04:13:00 -0000
Message-id: <000001c017f3$5c69c020$0800a8c0@win95.inteloop.se>
References: <39B57E79.EADD4317@webaxs.net>
X-SW-Source: 2000-09/msg00059.html
Content-length: 1007

> > > I think there should be a newsgroup for the gnu tools etc,
> > > for applications involving embedded systems. comp.arch.embedded
> > > is more hardware oriented.
> > > What about a comp.gnu.embedded for all questions on
> > > installation, development, use, and abuse of gnu/cygnus/open-source
> > > tools for embedded systems?
> >
> > How is the crossgcc mailing list not enough for you for this
> > purpose? That's exactly what it's for.
>
> Its just that crossgcc traffic seems a bit on the low side
> for some reason. BTW, is all this cross-posting bad? A
> newsgroup is better suited for a wide range of questions
> and seems more 'publicly accessible' for beginners to
> ask all kinds of stupid questions.

 I hope you haven't missed linux-embedded@waste.org. I'd also like to see a
comp.gnu.embedded newsgroup but not for the reason you stated. I like to
think we're all trying to help out anyone who spends time and effort to
research his problem and write coherent questions.


//Björnen.



             reply	other threads:[~2000-09-06  3:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-06  3:54 James Cownie [this message]
     [not found] <200009071009.e87A9oh14388@debye.wins.uva.nl>
2000-09-09 14:39 ` Peter.Schauer
     [not found] <20000901192328.A28312@valinux.com>
     [not found] ` <200009041047.LAA10659@phal.cygnus.co.uk>
     [not found]   ` <20000904084934.A11100@lucon.org>
     [not found]     ` <200009041751.e84HprD11517@debye.wins.uva.nl>
     [not found]       ` <20000904164458.A12270@lucon.org>
     [not found]         ` <200009050548.BAA05890@indy.delorie.com>
2000-09-04 23:32           ` H . J . Lu
     [not found] <Pine.LNX.4.21.0009041104140.3814-100000@propylaea.anduin.com>
2000-09-04 11:22 ` Ulrich Drepper

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=200009061054.GAA28894@albacore \
    --to=jcownie@etnus.com \
    --cc=gdb@sources.redhat.com \
    /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