Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [GDBserver] Remove td_ta_event_addr td_ta_set_event and td_ta_event_getmsg
Date: Mon, 01 Aug 2016 13:28:00 -0000	[thread overview]
Message-ID: <20160801132753.GA11734@blade.nx> (raw)
In-Reply-To: <1470043144-21617-1-git-send-email-yao.qi@linaro.org>

Hi Yao,

Yao Qi wrote:
> 2016-08-01  Yao Qi  <yao.qi@linaro.org>
> 
> 	* thread-db.c (struct thread_db) <td_ta_event_getmsg_p>: Remove.
> 	<td_ta_set_event_p, td_ta_event_addr_p>: Remove.
> 	(thread_db_load_search): Update.
> 	(try_thread_db_load_1): Don't look for td_ta_event_addr,
> 	td_ta_set_event and td_ta_event_getmsg.

Not an objection, but... are these still used in GDB native?
I'd really like to merge the two implementations at some point
in the next months.

Cheers,
Gary

-- 
http://gbenson.net/


  reply	other threads:[~2016-08-01 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01  9:19 Yao Qi
2016-08-01 13:28 ` Gary Benson [this message]
2016-08-01 16:14   ` Yao Qi
2016-08-02 11:18     ` Gary Benson
2016-08-02 15:07       ` Yao Qi

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=20160801132753.GA11734@blade.nx \
    --to=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@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