Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 13/17] btrace: non-stop
Date: Thu, 10 Sep 2015 11:19:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B23331ACE3E@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <55F163DD.4050809@redhat.com>

> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Thursday, September 10, 2015 1:05 PM
> To: Metzger, Markus T
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH 13/17] btrace: non-stop
> 
> On 09/10/2015 08:47 AM, Metzger, Markus T wrote:
> 
> > That seems to be the case.  I'm still getting the error I'm checking for before
> > the prompt, though, and my test will run into a timeout.
> >
> > 	thread apply all reverse-stepi 4 &
> >
> > 	Thread 2 (Thread 0x7ffff74fb700 (LWP 70895)):
> >
> > 	Thread 1 (Thread 0x7ffff7fcc740 (LWP 70891)):
> > 	Cannot execute this command while the selected thread is running.
> > 	(gdb) PASS: gdb.btrace/non-stop.exp: reverse-step: all: thread apply
> all reverse-stepi 4: prompt
> > 	0x0000000000400671      28        for (; i < 10; ++i) global += i; /* loop */
> > 	PASS: gdb.btrace/non-stop.exp: reverse-step: all: thread apply all
> reverse-stepi 4: thread 0
> > 	FAIL: gdb.btrace/non-stop.exp: reverse-step: all: thread apply all
> reverse-stepi 4: thread 1 (timeout)
> >
> > A failing run might take a bit longer, but that should be it.
> 
> Odd.  I'm running the test now for over 20 minutes, and it doesn't ever fail.
> Before I ran it against gdbserver for 10 minutes, never failed.
> This is with an i7-2620M; I hacked linux-btrace.c:intel_supports_bts to
> enable btrace.

I reverted one of the patches to trigger the error.  I wanted to see if
the test catches it.  The full series should run without error, of course.

This was meant to demonstrate that the error message precedes the
prompt.


> This looks good to me.  The comments above gdb_cont_to are stale though.

Thanks.  Will update.

Regards,
Markus.

Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul
Chairperson of the Supervisory Board: Tiffany Doon Silva
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


  reply	other threads:[~2015-09-10 11:19 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 10:36 [PATCH 00/17] record btrace: non-stop and ASNS Markus Metzger
2015-09-09 10:35 ` [PATCH 10/17] btrace: temporarily set inferior_ptid in record_btrace_start_replaying Markus Metzger
2015-09-09 10:35 ` [PATCH 08/17] btrace: lock-step Markus Metzger
2015-09-09 10:35 ` [PATCH 04/17] btrace: extract the breakpoint check from record_btrace_step_thread Markus Metzger
2015-09-09 10:35 ` [PATCH 05/17] btrace: split record_btrace_step_thread Markus Metzger
2015-09-09 10:35 ` [PATCH 15/17] btrace: allow full memory and register access for non-replaying threads Markus Metzger
2015-09-09 11:57   ` Pedro Alves
2015-09-09 10:35 ` [PATCH 12/17] infrun: switch to NO_HISTORY thread Markus Metzger
2015-09-09 10:35 ` [PATCH 01/17] btrace: fix non-stop check in to_wait Markus Metzger
2015-09-09 10:35 ` [PATCH 14/17] target, record: add PTID argument to to_record_is_replaying Markus Metzger
2015-09-09 10:35 ` [PATCH 11/17] btrace: async Markus Metzger
2015-09-09 10:35 ` [PATCH 03/17] btrace: improve stepping debugging Markus Metzger
2015-09-09 10:36 ` [PATCH 02/17] btrace: support to_stop Markus Metzger
2015-09-09 10:36 ` [PATCH 09/17] btrace: resume all requested threads Markus Metzger
2015-09-09 12:06   ` Pedro Alves
2015-09-09 13:06     ` Metzger, Markus T
2015-09-09 10:36 ` [PATCH 17/17] infrun: scheduler-locking reverse Markus Metzger
2015-09-09 13:54   ` Pedro Alves
2015-09-12 19:43     ` Jan Kratochvil
2015-09-15  9:29       ` Metzger, Markus T
2015-09-15 17:19         ` Jan Kratochvil
2015-09-16  7:59           ` Metzger, Markus T
2015-09-16 12:44             ` Metzger, Markus T
2015-09-16 13:23               ` Pedro Alves
2015-09-16 13:21             ` Pedro Alves
2015-09-17  8:39             ` Jan Kratochvil
2015-09-17  8:48               ` Metzger, Markus T
2015-09-17 10:11                 ` Eli Zaretskii
2015-09-09 10:36 ` [PATCH 13/17] btrace: non-stop Markus Metzger
2015-09-09 11:54   ` Pedro Alves
2015-09-09 12:20     ` Metzger, Markus T
2015-09-09 13:47       ` Pedro Alves
2015-09-09 14:10         ` Metzger, Markus T
2015-09-09 14:51           ` Pedro Alves
2015-09-10  7:49             ` Metzger, Markus T
2015-09-10 11:05               ` Pedro Alves
2015-09-10 11:19                 ` Metzger, Markus T [this message]
2015-09-10 11:32                   ` Pedro Alves
2015-09-10 11:37                     ` Metzger, Markus T
2015-09-10 12:48                       ` Pedro Alves
2015-09-09 10:36 ` [PATCH 07/17] btrace: add missing NO_HISTORY Markus Metzger
2015-09-09 10:36 ` [PATCH 16/17] target: add to_record_stop_replaying target method Markus Metzger
2015-09-09 11:59   ` Pedro Alves
2015-09-09 10:36 ` [PATCH 06/17] btrace: move breakpoint checking into stepping functions Markus Metzger
2015-09-09 13:56 ` [PATCH 00/17] record btrace: non-stop and ASNS Pedro Alves

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=A78C989F6D9628469189715575E55B23331ACE3E@IRSMSX104.ger.corp.intel.com \
    --to=markus.t.metzger@intel.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