From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: go32-nat, always a thread
Date: Fri, 08 Aug 2008 08:01:00 -0000 [thread overview]
Message-ID: <u3algj5qo.fsf@gnu.org> (raw)
In-Reply-To: <200808080439.17254.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Fri, 8 Aug 2008 04:39:17 +0100
>
> This patch makes the go32 (djgpp) target always register the main thread
> in GDB's thread table.
What do we need this for? DJGPP doesn't support threading; the ptid_t
variables in go32-nat.c are simply dummies devised to make the
compiler happy because go32-nat.c uses interfaces that pass thread
IDs. But there's no infrastructure behind this farce.
The code you added will now cause all kinds of notifications, like
"thread started", be displayed, which is just confusing when the
programmer knows there're no threads. Is this really justified?
> Anyone able to test this? Eli?
It's been a while since I built the DJGPP port, so I will probably
need a good vacation to do that again. But let's first decide if this
change is really necessary.
next prev parent reply other threads:[~2008-08-08 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 3:39 Pedro Alves
2008-08-08 3:41 ` Pedro Alves
2008-08-08 8:01 ` Eli Zaretskii [this message]
2008-08-08 12:43 ` Daniel Jacobowitz
2008-08-08 12:47 ` Eli Zaretskii
2008-08-08 12:55 ` Daniel Jacobowitz
2008-08-09 17:54 ` Pedro Alves
2008-08-09 18:06 ` Tom Tromey
2008-08-09 18:15 ` Pedro Alves
2008-08-09 18:22 ` Daniel Jacobowitz
2008-08-09 18:55 ` Eli Zaretskii
2008-08-09 19:18 ` Mark Kettenis
2008-08-09 19:31 ` Daniel Jacobowitz
2008-08-09 21:32 ` Eli Zaretskii
2008-08-09 21:33 ` Pedro Alves
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=u3algj5qo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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