From: Aleksandar Ristovski <aristovski@qnx.com>
To: Pedro Alves <palves@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/3] (patch 2/4, v2) [nto] Implement TARGET_OBJECT_AUXV.
Date: Tue, 20 Oct 2015 18:11:00 -0000 [thread overview]
Message-ID: <56267637.5050204@qnx.com> (raw)
In-Reply-To: <5626721A.5060808@qnx.com>
On 15-10-20 12:55 PM, Aleksandar Ristovski wrote:
> On 15-10-20 12:03 PM, Pedro Alves wrote:
>> On 10/20/2015 04:42 PM, Aleksandar Ristovski wrote:
>>> On 15-10-20 11:20 AM, Pedro Alves wrote:
>>>> Does this result in any visible improvement? I assume that
>>>> at least, "info auxv" now works [1] [2]. It'd be really nice to have a
>>>> blurb in the commit log mentioning what motivated this.
>>>
>>> Yes, info auxv works on a live process. For the core I have other
>>> patches that need to go in first, but the mechanism of getting auxv
>>> remains the same; only determining initial stack changes.
>>
>> OK, but please clarify or drop the misleading comment until
>> those patches go in then. Please push with that fixed.
>
Pushed now.
Thank you,
Aleksandar Ristovski
WARNING: multiple messages have this Message-ID
From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] (patch 2/4, v2) [nto] Implement TARGET_OBJECT_AUXV.
Date: Tue, 20 Oct 2015 18:39:00 -0000 [thread overview]
Message-ID: <56267637.5050204@qnx.com> (raw)
Message-ID: <20151020183900.tDGIbXfVi-2Bx4sD_3yBQtH4wMvi_n4glr0CVPTS5uE@z> (raw)
In-Reply-To: <5626721A.5060808@qnx.com>
On 15-10-20 12:55 PM, Aleksandar Ristovski wrote:
> On 15-10-20 12:03 PM, Pedro Alves wrote:
>> On 10/20/2015 04:42 PM, Aleksandar Ristovski wrote:
>>> On 15-10-20 11:20 AM, Pedro Alves wrote:
>>>> Does this result in any visible improvement? I assume that
>>>> at least, "info auxv" now works [1] [2]. It'd be really nice to have a
>>>> blurb in the commit log mentioning what motivated this.
>>>
>>> Yes, info auxv works on a live process. For the core I have other
>>> patches that need to go in first, but the mechanism of getting auxv
>>> remains the same; only determining initial stack changes.
>>
>> OK, but please clarify or drop the misleading comment until
>> those patches go in then. Please push with that fixed.
>
Pushed now.
Thank you,
Aleksandar Ristovski
next prev parent reply other threads:[~2015-10-20 17:13 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 16:01 [PATCH 0/4] [nto] Nto fixes Aleksandar Ristovski
2015-10-13 16:01 ` [PATCH 4/4] [nto] Setup signals Aleksandar Ristovski
2015-10-16 16:16 ` Pedro Alves
2015-10-22 15:57 ` Aleksandar Ristovski
2015-10-22 15:58 ` Aleksandar Ristovski
2015-10-13 16:01 ` [PATCH 3/4] [nto] Fix nto target stopped by watchpoint Aleksandar Ristovski
2015-10-16 16:10 ` Pedro Alves
2015-10-20 18:42 ` [PATCH 0/2] (patch 3/4 v2) Broken down patch 3/4 Aleksandar Ristovski
2015-10-20 19:24 ` [PATCH 2/2] [nto] Improve ABI sniffing Aleksandar Ristovski
2015-10-21 10:39 ` Pedro Alves
2015-10-21 14:47 ` Aleksandar Ristovski
2015-10-21 14:42 ` Aleksandar Ristovski
2015-10-21 15:17 ` Pedro Alves
2015-10-21 15:37 ` Aleksandar Ristovski
2015-10-21 16:13 ` Aleksandar Ristovski
2015-10-21 16:39 ` Pedro Alves
2015-10-21 18:23 ` Aleksandar Ristovski
2015-10-21 18:10 ` Aleksandar Ristovski
2015-10-21 8:18 ` [PATCH 1/2] [nto] Fix nto target stopped by watchpoint Aleksandar Ristovski
2015-10-21 10:39 ` Pedro Alves
2015-10-21 18:00 ` Aleksandar Ristovski
2015-10-21 17:51 ` Aleksandar Ristovski
2015-10-13 16:01 ` [PATCH 1/4] [nto] Fix nto build Aleksandar Ristovski
2015-10-15 17:34 ` Pedro Alves
2015-10-13 16:01 ` [PATCH 2/4] [nto] Fixes for nto procfs Aleksandar Ristovski
2015-10-15 17:41 ` Pedro Alves
2015-10-20 13:21 ` Aleksandar Ristovski
2015-10-20 12:43 ` Aleksandar Ristovski
2015-10-20 14:28 ` Pedro Alves
2015-10-20 14:28 ` [PATCH 0/3] (patch 2/4, v2) Break patch 2/4 into 3 Aleksandar Ristovski
2015-10-20 14:28 ` [PATCH 2/3] (patch 2/4, v2) [nto] Implement TARGET_OBJECT_AUXV Aleksandar Ristovski
2015-10-20 15:24 ` Pedro Alves
2015-10-20 16:03 ` Aleksandar Ristovski
2015-10-20 16:48 ` Pedro Alves
2015-10-20 17:08 ` Aleksandar Ristovski
2015-10-20 17:13 ` Aleksandar Ristovski
2015-10-20 18:11 ` Aleksandar Ristovski [this message]
2015-10-20 18:39 ` Aleksandar Ristovski
2015-10-20 18:11 ` Pedro Alves
2015-10-20 14:29 ` [PATCH 1/3] (patch 2/4, v2) [nto] Fixes for nto procfs Aleksandar Ristovski
2015-10-20 15:20 ` Pedro Alves
2015-10-20 17:13 ` Aleksandar Ristovski
2015-10-20 17:14 ` Aleksandar Ristovski
2015-10-20 15:03 ` [PATCH 3/3] (patch 2/4, v2) [nto] Implement procfs_pid_to_exec_file Aleksandar Ristovski
2015-10-20 15:25 ` Pedro Alves
2015-10-20 18:11 ` Aleksandar Ristovski
2015-10-20 18:19 ` Aleksandar Ristovski
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=56267637.5050204@qnx.com \
--to=aristovski@qnx.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