From: LRN <lrn1986@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
Date: Mon, 01 Oct 2012 22:48:00 -0000 [thread overview]
Message-ID: <506A1DB5.60901@gmail.com> (raw)
In-Reply-To: <m3k3v9byys.fsf@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02.10.2012 2:37, Sergio Durigan Junior wrote:
> On Wednesday, August 29 2012, LRN wrote:
>
>> To be a JIT-debugger [1] on Windows, gdb has to be able to signal
>> an event, which is passed to it by command line. If that is not
>> done, the process being debugged will not come out of a waiting
>> loop after gdb attaches to it.
>
> Sorry for being late on this thread, but do you have a copyright
> assignment on file for contributing for GDB? I don't see your name
> on gdb/MAINTAINERS.
I have a copyright assignment filed for GNUtls [1], would that suffice?
> If you do have it, please update gdb/MAINTAINERS.
I do not fit into any category. Not even Write After Approval
Maintainers, since i do not have write access to the GDB source tree.
[1]
http://git.savannah.gnu.org/gitweb/?p=gnutls.git;a=blob_plain;f=AUTHORS;hb=HEAD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQah20AAoJEOs4Jb6SI2Cw+GQIAM5HkDaoUvRPaxdNlhgv8B7J
MREnpwYSQ/uSFyrTZ3WXcZ59z12G8psoit3cgoh2DybUbh6Ht1I5zXHbLXYvM8Ku
KQy4QzDb0UA4q3tX2q2X9njA5owhbCIRUaLXatn3Xg+xJjpfaB5RZIe/pxcJ9Xqv
bhFcX2gfphvYQ+bQLFQEAXy/FSTZkq7J1JtvQwyxlejUtsWlfyNe4tl6fbDAGrpl
NnJuyFdtXvGOEHeN5CJOuZsWFAgqSzwtpfZEwH4LM4CkCN0Rgq5L6HDfiLHluzyw
MaQZ7rq5gZ+V+5ojt8M58pKN81bYrxzj2EGJlOBkou8uYMh9yNDCgLRXlHCQyes=
=KrHy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-10-01 22:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 17:55 LRN
2012-08-31 14:53 ` Eli Zaretskii
2012-08-31 15:37 ` Christopher Faylor
2012-08-31 15:40 ` LRN
2012-08-31 15:37 ` LRN
2012-09-10 2:22 ` LRN
2012-09-10 18:15 ` Tom Tromey
2012-09-10 18:32 ` LRN
2012-09-11 18:21 ` Pedro Alves
2012-09-11 18:27 ` LRN
2012-09-11 18:30 ` Pedro Alves
2012-09-11 18:09 ` Pedro Alves
2012-09-11 18:23 ` LRN
2012-09-11 18:27 ` Pedro Alves
2012-09-11 18:31 ` LRN
2012-09-29 12:42 ` LRN
2012-09-29 13:05 ` Eli Zaretskii
2012-09-29 19:32 ` LRN
2012-09-30 7:51 ` Eli Zaretskii
2012-09-30 12:46 ` LRN
2012-10-01 13:18 ` Eli Zaretskii
2012-10-01 16:22 ` LRN
2012-10-01 22:37 ` Sergio Durigan Junior
2012-10-01 22:48 ` LRN [this message]
2012-10-02 5:53 ` Sergio Durigan Junior
2012-10-02 12:48 ` Joel Brobecker
2012-10-02 12:57 ` LRN
2016-06-30 13:17 ` LRN
2016-06-30 15:25 ` Eli Zaretskii
2016-06-30 15:44 ` LRN
2016-06-30 16:23 ` Eli Zaretskii
2016-06-30 17:19 ` LRN
2016-06-30 17:42 ` Eli Zaretskii
2016-06-30 18:36 ` LRN
2016-06-30 18:57 ` Eli Zaretskii
2016-06-30 19:14 ` LRN
2016-07-02 1:16 ` LRN
2016-07-02 7:48 ` Eli Zaretskii
2016-07-10 13:06 ` LRN
2016-07-10 14:55 ` Eli Zaretskii
2016-07-18 10:08 ` LRN
2016-07-19 19:10 ` Eli Zaretskii
2016-07-20 4:43 ` LRN
2016-07-23 8:41 ` Eli Zaretskii
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=506A1DB5.60901@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