From: Andrew Cagney <ac131313@redhat.com>
To: "John S. Yates, Jr." <jyates@netezza.com>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: info threads
Date: Fri, 06 Jun 2003 21:31:00 -0000 [thread overview]
Message-ID: <3EE1083E.4090801@redhat.com> (raw)
In-Reply-To: <027701c31565$53c22b20$1400a8c0@astral>
> I have been implementing support for "info threads"
> based on the stock 5.3 release.
>
> For the qfThreadInfo message I return a list of the
> addresses of all TCBs (thread control blocks) known
> to our nucleus. It turns out that some of these
> live below the 2GB boundary and some above. Only
> those TCBs that do not appear to be negative are
> displayed. Why is this?
GDB would be showing its UNIX roots. Something is likely assuming that
any -ve is invalid. Excatly what, I don't know.
Andrew
next prev parent reply other threads:[~2003-06-06 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 13:25 John S. Yates, Jr.
2003-06-06 21:31 ` Andrew Cagney [this message]
2007-12-02 23:09 Brian Budge
2007-12-02 23:56 ` Daniel Jacobowitz
2007-12-03 21:29 ` Brian Budge
2007-12-04 3:30 ` Michael Snyder
2007-12-04 17:10 ` Jim Blandy
2007-12-04 19:22 ` Daniel Jacobowitz
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=3EE1083E.4090801@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jyates@netezza.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).