From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sources.redhat.com
Subject: thread id width
Date: Tue, 07 Sep 2004 10:49:00 -0000 [thread overview]
Message-ID: <5.2.0.9.1.20040907124018.01d3f280@NT_SERVER> (raw)
Hi
Some MI commands work with a 16bit hex encoded thread id (e.g. qC).
But then there's also qPmodethreadid where threadid is a 64bit value. And
some commands don't mention the size at all (vCont, TXX).
Is the limitation to 16bit still mandatory? Are there places in gdb that can't
cope with bigger ids? If so, why does the qP work with 64bit? For being
future-save?
Thanks
bye Fabi
reply other threads:[~2004-09-07 10:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5.2.0.9.1.20040907124018.01d3f280@NT_SERVER \
--to=cenedese@indel.ch \
--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