This is the mail archive of the 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] Thread exit messages on MS-Windows

On 2013-4-27 15:58, Eli Zaretskii wrote:
>> Date: Fri, 26 Apr 2013 12:46:56 +0300
>> From: Eli Zaretskii <>
>> This is from the node "Threads" of the manual:
>>   `set print thread-events'
>>   `set print thread-events on'
>>   `set print thread-events off'
>>        The `set print thread-events' command allows you to enable or
>>        disable printing of messages when GDB notices that new threads have
>>        started or that threads have exited.  By default, these messages
>>        will be printed if detection of these events is supported by the
>>        target.  Note that these messages cannot be disabled on all
>>        targets.
>> However, debugging MinGW programs on MS-Windows, I see only messages
>> about new threads, like this:
I'm not sure it is the correct behavior under Windows.
When debugging a single thread app, I do receive one New Thread message (for the main thread of the inferior), but there is not corresponding exit thread message report for this main thread. For multiply thread apps, the first New Thread messages has no corresponding exit messages, but other threads have both new and their corresponding exit messages.

Yuanhui Zhang

Corresponding messages have the same thread ID like:
[New Thread 2628.0xa4c]
[Thread 2628.0xa4c exited with code 0]

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