Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: James Clarke <jrtc27@jrtc27.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver
Date: Fri, 19 Jan 2018 22:35:00 -0000	[thread overview]
Message-ID: <351ACE0F-4C78-425C-B5C2-1025596942C1@jrtc27.com> (raw)
In-Reply-To: <63cbe53a-de3d-4413-b79b-ef6b34a951aa@redhat.com>

On 19 Jan 2018, at 18:39, Pedro Alves <palves@redhat.com> wrote:
> On 01/19/2018 05:22 PM, James Clarke wrote:
>> gdb/ChangeLog:
>> 	* gdbserver/linux-low.c (handle_extended_wait): Surround call to
>> 	thread_db_notice_clone with #ifdef USE_THREAD_DB, otherwise
>> 	linking fails with "undefined reference to
>> 	`thread_db_notice_clone(thread_info*, ptid_t)'" on architectures
>> 	without thread_db.
> 
> Note, we put the "why" info on the git commit log, not in the ChangeLog.

Ah, I think in the past I've ended up following that by chance, but it's useful
to know that as a rule.

> Also, gdb/ChangeLog -> gdb/gdbserver/ChangeLog.

Right, I should have noticed the extra ChangeLog file.

> I've amended those nits and pushed both patches in.

Thanks!

> AFAICT, you have a copyright assignment on file for other projects,
> but not for GDB.  The patches are small enough for that to not be
> an issue, but if you're planning on contributing more, it'll be
> good to take care of that.

Yeah, sure, I hope that I don't need to make any future fixes but who knows.

Thanks,
James


      reply	other threads:[~2018-01-19 22:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 17:23 [PATCH v2 1/2] gdb: Fix ia64 defining TRAP_HWBKPT before including gdb_wait.h James Clarke
2018-01-19 17:23 ` [PATCH v2 2/2] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver James Clarke
2018-01-19 18:39   ` Pedro Alves
2018-01-19 22:35     ` James Clarke [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=351ACE0F-4C78-425C-B5C2-1025596942C1@jrtc27.com \
    --to=jrtc27@jrtc27.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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