This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: go32-nat, always a thread


> 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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]