From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: gdb@sources.redhat.com
Subject: Thread ID in gdbserver
Date: Mon, 06 Jun 2005 05:25:00 -0000 [thread overview]
Message-ID: <20050606.142517.51862870.nemoto@toshiba-tops.co.jp> (raw)
Hi. In Mar 2005, the type of cont_thread, stop_thread, etc. was
changed to "unsigned long" from "int". But there are still some codes
which assume these variables are signed numbers.
For example, in gdbserver/server.c:
unsigned long cont_thread;
...
if (n == 1 && resume_info[0].thread != -1)
cont_thread = resume_info[0].thread;
else
cont_thread = -1;
...
if (step || sig || cont_thread > 0)
This looks very suspicious.
For now I do not know whether this is real problem, but it is
potential bug and should be fixed, isn't it?
---
Atsushi Nemoto
next reply other threads:[~2005-06-06 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 5:25 Atsushi Nemoto [this message]
2005-06-06 13:46 ` 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=20050606.142517.51862870.nemoto@toshiba-tops.co.jp \
--to=anemo@mba.ocn.ne.jp \
--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