Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Tristan Gingold <gingold@adacore.com>
Subject: Re: [RFC] How to get target_ops from to_kill method?
Date: Tue, 17 Mar 2009 19:31:00 -0000	[thread overview]
Message-ID: <20090317192851.GE31979@adacore.com> (raw)
In-Reply-To: <200903171911.25347.pedro@codesourcery.com>

> >         * target.h (struct target_ops): Add a "target_ops *" parameter to
> >         method to_kill.
> >         (target_kill): Remove macro. Add declaration.
> >         * target.c (debug_to_kill): Delete, no longer necessary.
> >         (target_kill): New function.
> >         (update_current_target):  Stop inheriting the to_kill method.
> >         Do not de_fault it to no_process either.
> >         (setup_target_debug): Do not set current_target.to_kill.
> >         * gnu-nat.c, go32-nat.c, hpux-thread.c, inf-ptrace.c, inf-ttrace.c,
> >         linux-nat.c, monitor.c, nto-procfs.c, procfs.c, remote-m32r-sdi.c,
> >         remote-mips.c, remote-sim.c, remote.c, windows-nat.c: Update
> >         accordingly.
> > 
> > Tested on x86_64-linux again...
> 
> This looks great.  Please go ahead and commit it.  Thanks!

Yoohoo! Thanks a lot for your help, Pedro. Much appreciated.

-- 
Joel


      reply	other threads:[~2009-03-17 19:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 16:42 Joel Brobecker
2009-03-16 17:02 ` Pedro Alves
2009-03-16 17:24   ` Joel Brobecker
2009-03-16 17:24     ` Pedro Alves
2009-03-16 19:07       ` Joel Brobecker
2009-03-16 22:22         ` Joel Brobecker
2009-03-17  0:05           ` Pedro Alves
2009-03-17 18:05             ` Joel Brobecker
2009-03-17 18:28               ` Pedro Alves
2009-03-17 19:11                 ` Joel Brobecker
2009-03-17 19:13                   ` Pedro Alves
2009-03-17 19:31                     ` Joel Brobecker [this message]

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=20090317192851.GE31979@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=pedro@codesourcery.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