From: Carl Love <cel@us.ibm.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Luis Machado <luis.machado@arm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>,
gdb@sourceware.org, buildbot@sourceware.org
Subject: RE: [builder] gdb_check_step: remove gdb.gdb/selftest.exp
Date: Fri, 10 Jun 2022 13:11:23 -0700 [thread overview]
Message-ID: <aa46b3156f4db7494502009db59c0ab8dfcafc5d.camel@us.ibm.com> (raw)
In-Reply-To: <YqOXaPHOMAVU7f3G@wildebeest.org>
Mark:
On Fri, 2022-06-10 at 21:11 +0200, Mark Wielaard wrote:
> Hi Carl,
>
> On Fri, Jun 10, 2022 at 08:54:00AM -0700, Carl Love wrote:
> > On Fri, 2022-06-10 at 11:58 +0100, Luis Machado wrote:
> > > On 6/10/22 11:50, Mark Wielaard wrote:
> > > > On Fri, 2022-06-10 at 01:21 +0200, Mark Wielaard wrote:
> > > > > On Fri, Jun 10, 2022 at 01:09:19AM +0200, Mark Wielaard
> > > > > wrote:
> > > > > > On Thu, Jun 09, 2022 at 10:37:58AM +0100, Luis Machado
> > > > > > wrote:
> > > > > > > I always use gdb.base/break.exp as a good smoke test. If
> > > > > > > that
> > > > > > > one
> > > > > > > fails, then things
> > > > > > > are really broken.
> > > > > > >
> > > > > > > I think gdb.base/break*.exp should make a good smoke test
> > > > > > > list.
> > > > > > > We just need to exclude
> > > > > > > gdb.base/break-interp.exp, which is problematic on some
> > > > > > > targets.
> >
> > Trying to to understand how you are running the test. I think you
> > are
> > running these as remote tests, i.e. machine A requests that a
> > remote
> > machine B run the test via gdbserver, correct?
>
> Yes, but machine A and B are the same one in this case. The tests
> are
> run three times. Once with just gdb, and then with a target-board set
> to either native-gdbserver or native-extended-gdbserver.
>
> The buildbot log stdio should show you the exact settings.
>
> https://builder.sourceware.org/buildbot/#/builders/76/builds/446/steps/12/logs/stdio
>
> make -j4 check-gdb 'TESTS= gdb.base/break-always.exp gdb.base/break-
> caller-line.exp gdb.base/break-entry.exp gdb.base/break.exp
> gdb.base/break-fun-addr.exp gdb.base/break-idempotent.exp
> gdb.base/break-include.exp gdb.base/break-inline.exp gdb.base/break-
> main-file-remove-fail.exp gdb.base/break-on-linker-gcd-function.exp
> gdb.base/breakpoint-in-ro-region.exp gdb.base/breakpoint-shadow.exp
> gdb.base/break-probes.exp gdb.gdb/unittest.exp
> gdb.server/unittest.exp ' 'RUNTESTFLAGS="--target_board=native-
> gdbserver"'
>
> So it is the RUNTESTFLAGS="--target_board=native-gdbserver" that
> tells
> the test to run against the native-gdbserver.
OK, thanks that will be helpful for testing.
So, I have been trying to isolate where the messages
ERROR: no fileid for ltcd97-lp2
ERROR: Couldn't send delete breakpoints to GDB.
ERROR: can't read "gdb_spawn_id": no such variable
Looks like a couple of the error messages are coming from proc
default_gdb_exit. The routine is called as part of the check in the
original test program. The break-idempotent.exp calls
skip_hw_watchpoint_tests which calls has_hw_wp_support which calls
gdb_exit which calls proc default_gdb_exit. In default_gdb_exit we
have:
if ![is_remote host] {
remote_close host <- generates ERROR: no fileid for ltcd97-lp2
}
unset gdb_spawn_id <- generates ERROR: can't read "gdb_spawn_id": no such variable
unset ::gdb_tty_name
unset inferior_spawn_id
So, now to figure out why those statements are failing....???
Carl
next prev parent reply other threads:[~2022-06-10 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 18:51 Mark Wielaard
2022-06-09 9:37 ` Luis Machado
2022-06-09 23:09 ` Mark Wielaard
2022-06-09 23:21 ` Mark Wielaard
2022-06-10 10:50 ` Mark Wielaard
2022-06-10 10:58 ` Luis Machado
2022-06-10 15:17 ` will schmidt
2022-06-10 15:54 ` Carl Love
2022-06-10 19:11 ` Mark Wielaard
2022-06-10 20:11 ` Carl Love [this message]
2022-06-10 22:23 ` Frank Ch. Eigler
2022-06-29 15:58 ` Carl Love
2022-06-29 22:42 ` Mark Wielaard
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=aa46b3156f4db7494502009db59c0ab8dfcafc5d.camel@us.ibm.com \
--to=cel@us.ibm.com \
--cc=buildbot@sourceware.org \
--cc=gdb@sourceware.org \
--cc=luis.machado@arm.com \
--cc=mark@klomp.org \
--cc=will_schmidt@vnet.ibm.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).