Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>,
	 gdb@sourceware.org,  lee.jones@linaro.org
Subject: Re: RFC GDB Linux Awareness analysis
Date: Thu, 01 Oct 2015 09:25:00 -0000	[thread overview]
Message-ID: <868u7n6iuq.fsf@gmail.com> (raw)
In-Reply-To: <20150930132729.GB26183@griffinp-ThinkPad-X1-Carbon-2nd> (Peter	Griffin's message of "Wed, 30 Sep 2015 14:27:29 +0100")

Peter Griffin <peter.griffin@linaro.org> writes:

> Does anyone have experience / thoughts on how often the existing threading
> implementations that are already inside GDB break? Presumably these are also
> tightly coupled to parsing out of tree data structures (or the libraries which
> GDB relies on to do this).

It shouldn't break in any case.  There are some conventions in these
thread libraries to make it debuggable.  In glibc NPTL,
__nptl_create_event should be called after a thread is created.  GDB
relies on this, and set a breakpoint on it to monitor the thread
creation.  In AIX thread lib, GDB replies on the symbol name returned by
pthdb_session_pthreaded, and set a breakpoint on it similarly.

We need linux kernel to have such convention with GDB, that is, a
function is called after a thread is created, and the function name
shouldn't be changed across different version of kernels.

-- 
Yao (齐尧)


  parent reply	other threads:[~2015-10-01  9:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150603142858.GA19370@griffinp-ThinkPad-X1-Carbon-2nd>
2015-08-20 18:22 ` Andreas Arnez
2015-09-30 13:27   ` Peter Griffin
2015-09-30 16:41     ` Duane Ellis
2015-10-05 18:32       ` Doug Evans
2015-10-01  9:25     ` Yao Qi [this message]
2015-10-02 10:56     ` Andreas Arnez
2015-10-05 18:54 duane
2015-10-05 19:41 ` Doug Evans

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=868u7n6iuq.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb@sourceware.org \
    --cc=lee.jones@linaro.org \
    --cc=peter.griffin@linaro.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