Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: LRN <lrn1986@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Bug win32/14529] Make gdb capable of JIT-debugging on W32
Date: Tue, 02 Oct 2012 05:53:00 -0000	[thread overview]
Message-ID: <m3626t8lne.fsf@redhat.com> (raw)
In-Reply-To: <506A1DB5.60901@gmail.com> (LRN's message of "Tue, 02 Oct 2012	02:48:21 +0400")

On Monday, October 01 2012, LRN wrote:

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

Not sure, we will probably have to ask someone else.  Maybe some GM
knows the answer?

Anyway, if you have a GNU copyright assignment for a project, I guess it
is much easier to extend this to other project.

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

That's because you do not have a copyright assignment for GDB.  *If your
patch is approved and committed*, you can ask for Write After Approval
at <http://sourceware.org/cgi-bin/pdw/ps_form.cgi>, and then you will be
able to update gdb/MAINTAINERS.

Thanks,

-- 
Sergio


  reply	other threads:[~2012-10-02  5:53 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   ` 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-08-31 15:37   ` Christopher Faylor
2012-08-31 15:40     ` LRN
2012-10-01 22:37 ` Sergio Durigan Junior
2012-10-01 22:48   ` LRN
2012-10-02  5:53     ` Sergio Durigan Junior [this message]
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=m3626t8lne.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lrn1986@gmail.com \
    /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