Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH V2 0/5] Support tracepoints for ARM linux in GDBServer
Date: Wed, 09 Nov 2016 17:58:00 -0000	[thread overview]
Message-ID: <wwok60nwsfhm.fsf@ericsson.com> (raw)
In-Reply-To: <CAH=s-PPnFU8AMRMWB0prcCXFSckWqtaFtC6-naXOWqQjUpqTRw@mail.gmail.com>


Yao Qi writes:

> On Tue, Nov 8, 2016 at 1:28 AM, Antoine Tremblay
> <antoine.tremblay@ericsson.com> wrote:
>>
>
>>>
>>> I am still testing arm-linux gdbserver without and with software
>>> single step.  I still see some intermittent regressions _with_
>>> software single step,
>>>
>>> +FAIL: gdb.threads/non-stop-fair-events.exp: signal_thread=8: thread 1
>>> broke out of loop (timeout)
>>> +FAIL: gdb.threads/schedlock.exp: schedlock=off: cmd=step: step to
>>> increment (1) (timeout)
>>>
>>
>> I have not seen that except when I get random SIGILLs, I'll try to run
>> these more often and see if I can reproduce it.
>>
>
> I have two boards for testing pandaboard (3.4.0-2-linaro-lt-omap)
> and chromebook (4.7.2).  I got non-stop-fair-events.exp timeout
> from time to time, you can get gdb.log here,
> http://people.linaro.org/~yao.qi/gdb/arm-linux-tracepoint/non-stop-fair-events/
>
> I can also see SIGILL or SIGSEGV in schedlock.exp,
> http://people.linaro.org/~yao.qi/gdb/arm-linux-tracepoint/schedlock/
>
> if I hack gdbserver/linux-low.c to disable software single step,
>  static int
>  can_software_single_step (void)
>  {
> -  return (the_low_target.get_next_pcs != NULL);
> +  return 0/*(the_low_target.get_next_pcs != NULL)*/;
>  }
>
> the fails goes away.
>

OK, thanks for the description, I can now reproduce it on my Odroid UX4
and I have a good idea where the problem is now (some cases of
installing the software breakpoitns are done without stopping the threads).

So I should be able to fix this soon.

>>> This reveals something wrong in software single step in GDBserver.
>>> I don't think we should bring tracepoint in until these regressions are
>>> fixed.I won't work on these regressions until next pre-release.  If
>>> you can reproduce them and help to fix them, that will be great.
>>
>> I will do my best to fix these issues asap,
>>
>> However I would very much like if we could still start the review
>> process on the tracing.
>
> I'll play with them, and give some review later.

Thank you very much, hopefully I'll have the fix for the issue by then
too.

Antoine


      reply	other threads:[~2016-11-09 17:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 14:33 Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 4/5] Use FAST_TRACEPOINT_LABEL in range-stepping.exp Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 2/5] Enable tracing of pseudo-registers on ARM Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 5/5] Support tracepoints for ARM linux in GDBServer Antoine Tremblay
2016-11-03 17:51   ` Eli Zaretskii
2016-11-03 18:12     ` Antoine Tremblay
2016-11-10 14:01   ` Yao Qi
2016-11-15 14:42     ` Antoine Tremblay
2016-11-16 20:49       ` Yao Qi
2016-11-03 14:33 ` [PATCH V2 1/5] Teach arm unwinders to terminate gracefully Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 3/5] Improve tests to allow for targets that support trace but not ftrace Antoine Tremblay
2016-11-07  9:25 ` [PATCH V2 0/5] Support tracepoints for ARM linux in GDBServer Yao Qi
     [not found]   ` <wwoka8dasqta.fsf@ericsson.com>
2016-11-08 15:34     ` Antoine Tremblay
2016-11-09 16:39     ` Yao Qi
2016-11-09 17:58       ` Antoine Tremblay [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=wwok60nwsfhm.fsf@ericsson.com \
    --to=antoine.tremblay@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.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