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>,
	"gdb-patches@sourceware.org"	<gdb-patches@sourceware.org>
Subject: RE: [PATCH v3 5/5] btrace, testsuite: fix extended-remote fail
Date: Tue, 31 Jan 2017 16:06:00 -0000	[thread overview]
Message-ID: <A78C989F6D9628469189715575E55B2340046F7F@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <217e1c28-070a-f485-aa06-a91f69c31023@redhat.com>

> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Tuesday, January 31, 2017 2:00 PM
> To: Metzger, Markus T <markus.t.metzger@intel.com>; gdb-
> patches@sourceware.org
> Subject: Re: [PATCH v3 5/5] btrace, testsuite: fix extended-remote fail
> 
> On 01/30/2017 10:05 AM, Markus Metzger wrote:
> > Parts of gdb.btrace/enable.exp are only valid for native debug.  The check for
> > skip_gdbserver_tests is done while GDB is running, though, which causes it to
> > fail with --target_board=native-extended-gdbserver.  Exit GDB before that
> check.
> >
> 
> Can you clarify how it fails?  It's not obvious to me from looking at
> skip_gdbserver_tests.

spawn /nfs/site/disks/idb_team/mmetzger/gdb/build/ulll001/gdb/testsuite/../gdbserver/gdbserver --once --multi :2349
Listening on port 2349
target extended-remote localhost:2349
Already connected to a remote target.  Disconnect? (y or n) ^CQuit
(gdb) set tdesc filename /nfs/site/disks/idb_team/mmetzger/gdb/build/ulll001/gdb/testsuite/outputs/gdb.btrace/enable/tri
vial.xml
(gdb) n
The program is not being run.
(gdb) FAIL: gdb.btrace/enable.exp: set tdesc filename /nfs/site/disks/idb_team/mmetzger/gdb/build/ulll001/gdb/testsuite/outputs/gdb.btrace/enable/trivial.xml (got interactive prompt)
monitor exit


There's a comment in lib/gdb.exp before gdb_skip_xml_test, which is called
by skip_gdbserver_tests:

	# Return true if a test should be skipped due to lack of XML support
	# in the host GDB.
	# NOTE: This must be called while gdb is *not* running.

	gdb_caching_proc gdb_skip_xml_test {


I thought this is supposed to be general knowledge so I didn't bother to go into more
detail in the commit message.


> Should we add something like:
> 
>     global gdb_spawn_id
>     if {[info exists gdb_spawn_id]} {
>       	error "....."
> 	return
>     }
> 
> ... to skip_gdbserver_tests ?

That would certainly make it more obvious:

	Running .../gdb.btrace/enable.exp ...
	ERROR: tcl error sourcing .../gdb.btrace/enable.exp.
	ERROR: GDB must not be running in skip_gdbserver_tests.
	    while executing
	"error "GDB must not be running in skip_gdbserver_tests.""
	    (procedure "skip_gdbserver_tests" line 9)
	    invoked from within
	"skip_gdbserver_tests"
	    invoked from within
	"if [skip_gdbserver_tests] {
	    unsupported "target does not support gdbserver"
	    return 0
	}"
	    (file ".../gdb.btrace/enable.exp" line 83)
	    invoked from within
	"source .../gdb.btrace/enable.exp"
	    ("uplevel" body line 1)
	    invoked from within
	"uplevel #0 source /.../gdb.btrace/enable.exp"
	    invoked from within
	"catch "uplevel #0 source $test_file_name""

Looks like we don't need the return, though.  And the check should
probably go into skip_xml_tests.  Let me add a separate patch for this.

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, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


  reply	other threads:[~2017-01-31 16:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 10:05 [PATCH v3 0/5] thread, btrace: allow "record btrace" for running threads Markus Metzger
2017-01-30 10:05 ` [PATCH v3 4/5] btrace, testsuite: fix extended-remote non-stop test Markus Metzger
2017-01-31 13:00   ` Pedro Alves
2017-01-30 10:06 ` [PATCH v3 5/5] btrace, testsuite: fix extended-remote fail Markus Metzger
2017-01-31 13:00   ` Pedro Alves
2017-01-31 16:06     ` Metzger, Markus T [this message]
2017-01-31 16:42       ` Pedro Alves
2017-01-30 10:06 ` [PATCH v3 1/5] thread: add can_access_registers_ptid Markus Metzger
2017-01-30 10:06 ` [PATCH v3 3/5] btrace: add unsupported/untested messages when skipping tests Markus Metzger
2017-01-31 13:00   ` Pedro Alves
2017-01-30 10:06 ` [PATCH v3 2/5] btrace: allow recording to be started (and stopped) for running threads Markus Metzger
2017-01-31 12:59   ` Pedro Alves
2017-01-31 16:06     ` Metzger, Markus T
2017-01-31 16:36       ` Pedro Alves
2017-02-01  8:53         ` Metzger, Markus T
2017-02-01  9:08           ` Metzger, Markus T
2017-02-01 10:40             ` 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=A78C989F6D9628469189715575E55B2340046F7F@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