From: LRN <lrn1986@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: Program-assigned thread names on Windows
Date: Wed, 10 Aug 2016 23:42:00 -0000 [thread overview]
Message-ID: <0926f8a1-8f4b-958b-416d-52c7595b5bd8@gmail.com> (raw)
In-Reply-To: <9f602f70-b7de-7433-dbd1-61bdc328b6a9@redhat.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 817 bytes --]
On 10.08.2016 21:45, Pedro Alves wrote:
> On 08/10/2016 06:54 PM, LRN wrote:
>
> Maybe I could convince you to implement this in gdbserver/win32-low.c too?
You can't. I've never used gdbserver, and i don't see any need for me to
start using it. And since i don't use it, i wouldn't be able to test
anything code changes i could introduce there.
TBH, i don't have any plans for further contributions to gdb. There is only
one more feature that i thought could be added (using Windows API to obtain
stack traces, enhancing the built-in gdb stack walker; thus gdb would be
able to show useful stack trace even while being deep inside W32 API
calls), but the code was so complicated for me that i've failed to even
*find* where to start.
--
O< ascii ribbon - stop html email! - www.asciiribbon.org
[-- Attachment #1.1.2: 0x6759BA74.asc --]
[-- Type: application/pgp-keys, Size: 3540 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-10 23:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 9:25 LRN
2016-07-23 9:33 ` Eli Zaretskii
2016-07-23 9:43 ` LRN
2016-07-23 10:18 ` Eli Zaretskii
2016-07-23 16:43 ` John Baldwin
2016-07-23 17:01 ` LRN
2016-07-25 12:17 ` Jon Turney
2016-07-25 13:34 ` LRN
2016-07-25 14:07 ` Jon Turney
[not found] ` <e50e62e8-b3a8-cd4a-aff0-ea2097cf2412@gmail.com>
2016-07-25 21:33 ` LRN
2016-07-26 6:08 ` LRN
2016-07-26 13:18 ` Jon Turney
2016-07-26 14:17 ` LRN
2016-07-26 15:41 ` LRN
2016-07-26 17:15 ` LRN
2016-07-26 22:20 ` Jon Turney
2016-07-27 21:35 ` Jon Turney
2016-07-28 7:21 ` LRN
2016-08-02 9:47 ` LRN
2016-08-02 14:55 ` Eli Zaretskii
2016-08-10 7:12 ` LRN
2016-08-10 12:15 ` Pedro Alves
2016-08-10 17:54 ` LRN
2016-08-10 18:45 ` Pedro Alves
2016-08-10 23:42 ` LRN [this message]
2016-08-11 0:39 ` 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=0926f8a1-8f4b-958b-416d-52c7595b5bd8@gmail.com \
--to=lrn1986@gmail.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).