From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Omair Javaid <omair.javaid@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] Fixes for aarch64-linux gdb core file support
Date: Wed, 04 Jun 2014 17:11:00 -0000 [thread overview]
Message-ID: <87y4xc4n2c.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <1401898871-2270-3-git-send-email-omair.javaid@linaro.org> (Omair Javaid's message of "Wed, 4 Jun 2014 21:21:06 +0500")
On Wed, Jun 04 2014, Omair Javaid wrote:
> This patch fixes aarch64 linux core file support by adding/updating
> aarch64-linux supply/collect methods for aarch64 register set.
Have you looked at that patch?
https://sourceware.org/ml/gdb-patches/2014-05/msg00637.html
Apart from 'core_regset_sections', I believe it provides the same
functionality as this patch, right?
next prev parent reply other threads:[~2014-06-04 17:11 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 16:21 [PATCH 0/7] Process record and reverse debugging support on aarch64-linux Omair Javaid
2014-06-04 16:21 ` [PATCH 1/7] NEWS entry about aarch64-linux record/replay support Omair Javaid
2014-06-04 16:24 ` Eli Zaretskii
2014-08-30 2:40 ` Yao Qi
2014-09-01 14:51 ` Marcus Shawcroft
2014-09-02 1:01 ` Yao Qi
2014-09-17 23:30 ` [PATCH] " Omair Javaid
2014-09-18 2:53 ` Eli Zaretskii
2014-06-04 16:21 ` [PATCH 4/7] Implements aarch64 process record and reverse debugging support Omair Javaid
2014-06-05 8:34 ` Will Newton
2014-08-28 22:17 ` Omair Javaid
2014-08-30 3:27 ` Yao Qi
2014-09-01 20:08 ` Omair Javaid
2014-09-18 0:09 ` Omair Javaid
2014-09-18 22:29 ` Omair Javaid
2014-10-14 12:48 ` Omair Javaid
2014-10-21 9:08 ` Omair Javaid
2014-06-04 16:21 ` [PATCH 7/7] Enables gdb.reverse testsuite for aarch64*-linux targets Omair Javaid
2014-06-05 9:00 ` Will Newton
2014-10-21 9:10 ` Omair Javaid
2014-06-04 16:21 ` [PATCH 6/7] Support for recording aarch64 advance simd instructions Omair Javaid
2014-06-05 8:58 ` Will Newton
2014-08-29 13:41 ` [PATCH 6/7] Support for recording aarch64 advanced SIMD instructions Omair Javaid
2014-09-02 15:01 ` Will Newton
2014-06-04 16:21 ` [PATCH 5/7] Support for recording syscall on aarch64-linux Omair Javaid
2014-06-05 8:52 ` Will Newton
2014-06-06 15:58 ` Andreas Arnez
2014-06-11 7:11 ` Omair Javaid
2014-08-29 11:53 ` Omair Javaid
2014-09-18 0:23 ` Will Newton
2014-09-18 22:28 ` Omair Javaid
2014-10-14 12:47 ` Omair Javaid
2014-10-21 9:09 ` Omair Javaid
2014-06-04 16:21 ` [PATCH 3/7] Enable gdb process record on aarch64-linux targets Omair Javaid
2014-06-05 9:00 ` Will Newton
2014-08-30 3:35 ` Yao Qi
2014-09-01 19:50 ` Omair Javaid
2014-06-04 16:21 ` [PATCH 2/7] Fixes for aarch64-linux gdb core file support Omair Javaid
2014-06-04 17:11 ` Andreas Arnez [this message]
2014-06-05 17:09 ` Omair Javaid
2014-08-28 13:49 ` [PATCH 2/7] Fixes for aarch64-linux " Omair Javaid
2014-08-30 3:00 ` Yao Qi
2014-09-01 19:38 ` Omair Javaid
2014-09-17 23:37 ` Re " Omair Javaid
2014-10-14 12:49 ` Omair Javaid
2014-10-21 9:07 ` Omair Javaid
2014-10-21 13:28 ` Yao Qi
2014-10-27 12:33 ` Omair Javaid
2014-06-05 9:07 ` [PATCH 2/7] Fixes for aarch64-linux gdb " Will Newton
2014-06-23 10:41 ` [PATCH 0/7] Process record and reverse debugging support on aarch64-linux Omair Javaid
2014-08-30 3:45 ` Yao Qi
2014-09-01 19:42 ` Omair Javaid
2014-09-02 1:12 ` 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=87y4xc4n2c.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=omair.javaid@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