public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Omair Javaid <omair.javaid@linaro.org>
To: oza Pawandeep <oza.pawandeep@gmail.com>
Cc: Yao Qi <yao@codesourcery.com>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	patches <patches@linaro.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH 0/2] GDB process record and reverse debugging improvements for arm*-linux*
Date: Mon, 11 Nov 2013 08:25:00 -0000	[thread overview]
Message-ID: <52809426.40405@linaro.org> (raw)
In-Reply-To: <CAK1A=4wzJUDvTEX6SxL_dEHaDvx7H0MaLShfEcN8e-RTSOHWmw@mail.gmail.com>

On Fri 08 Nov 2013 01:18:45 PM PKT, oza Pawandeep wrote:
> Hi,
>
> The previous support for arm instruction and thumb instruction for
> record and reply was added by me.
> but there some reverse test case failing...
> I had issues with employer disclaimer, so could not proceed.
> I have got the disclaimer now and is up-to date with FSF.
>
> some of the queries to you regarding thumb2 support ?
>
> 1) did you bring in co processor and dsp instruction support for thumb2 ?
>
> 2) can you please run gdb-rever test suite and see if your code passes
> the same ?
>
>
> Regards,
> Oza.
>
>
> On Fri, Nov 8, 2013 at 12:55 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>>> Date: Fri, 08 Nov 2013 08:18:35 +0500
>>> From: Omair Javaid <omair.javaid@linaro.org>
>>> CC: gdb-patches@sourceware.org, Patch Tracking <patches@linaro.org>
>>>
>>> --- gdb/NEWS  11 Oct 2013 13:51:26 -0000      1.622
>>> +++ gdb/NEWS  7 Nov 2013 23:58:26 -0000
>>> @@ -3,6 +3,10 @@
>>
>> This part is OK, but please make sure to have 2 spaces between
>> sentences
>>
>>> +* Improved support of process record-replay and reverse debugging on
>>> +  arm*-linux* targets. Support for thumb32 and syscall instructions
>>                          ^^
>> here.
>>
>> Thanks.
>

Hello Oza,

I really appreciate your work on arm process record and I am trying to 
improve on the work you have done previously. I have sent 3 patches 
upstream which include basic support for Thumb32 instructions and 
system call instructions along with some fixes.

There were around 1500 failures in gdb.reverse on arm that have been 
significantly reduced. Here is a current status of gdb.reverse test 
suite on arm targets:

arm-native configuration:
# of expected passes		2253
# of unexpected failures	71

arm-remote configuration:
# of expected passes		2142
# of unexpected failures	122

I am currently working on patches to fix above unexpected failures and 
also working on supporting co-processor and other unsupported 
instruction types.

--
Omair.

  reply	other threads:[~2013-11-11  8:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  0:09 Omair Javaid
2013-10-24  1:42 ` Yao Qi
2013-10-24  1:44 ` Yao Qi
2013-11-08  3:20   ` Omair Javaid
2013-11-08  8:04     ` Eli Zaretskii
2013-11-08  8:21       ` oza Pawandeep
2013-11-11  8:25         ` Omair Javaid [this message]
2013-11-24 23:49           ` Omair Javaid
2013-11-25  4:56             ` Eli Zaretskii
2013-12-17 10:22               ` Omair Javaid
2013-12-20 12:38             ` Pedro Alves
2014-01-03 19:20               ` Omair Javaid

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=52809426.40405@linaro.org \
    --to=omair.javaid@linaro.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=oza.pawandeep@gmail.com \
    --cc=patches@linaro.org \
    --cc=yao@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).