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: [RFA 2/2][master only] gdb/windows-nat.c: Get rid of main_thread_id global


> Date: Wed, 17 Apr 2019 10:38:42 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> It happens completely randomly, and in all cases, the program itself
> has a main program which waits for all software threads to complete
> before itself terminating. Not sure what Windows is doing under
> the hood.

At program termination time, all kinds of irregularities could happen,
especially if the program doesn't exit by exiting 'main' -- because
AFAIK doing the latter causes CRT to explicitly shut down all the
other threads.

But there's little doubt in my mind that the thread whose ID is
reported by CREATE_PROCESS_DEBUG_EVENT is the main thread.

> If I understand you correctly, you want to preserve the global
> so we can avoid those notifications. In my opinion, doing that
> just for the purpose of filtering one notification is simply
> not worth the trouble of keeping a global around.  Generally speaking,
> we tend to try to avoid globals as much as we can, as they are hard to
> track, and makes the code harder to understand and maintain.
> Modifying the logic to use the main_thread_id global instead of
> the kind of event is a step backwards, in my opinion.

If the only problem is having the global variable, we could mark the
main thread in some other way, that won't need the global.

But yes, I think not announcing the main thread is a nice feature, and
losing it due to the mess that happens at program exit (something to
which most users won't pay attention anyway) would be a pity.  I'd
even agree to announcing the exit of the main thread, if we cannot
come up with a better solution, if that could allow us avoid its
announcement at program startup.

The use case I have in mind is debugging a single-threaded program.
It is jarring enough, when debugging such a program, to see GDB
announcing threads started by the OS.  It would be nice if we could
avoid announcing the main thread.

Thanks.


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