This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PING 2][PATCH v3] Add pretty printers for the NPTL lock types
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Martin Galvan <martin dot galvan at tallertechnologies dot com>
- Cc: Joseph Myers <joseph at codesourcery dot com>, Siddhesh Poyarekar <sid at reserved-bit dot com>, libc-alpha at sourceware dot org, Tom Tromey <tom at tromey dot com>, Torvald Riegel <triegel at redhat dot com>, Pedro Alves <palves at redhat dot com>, vapier at gentoo dot org, Daniel Gutson <daniel dot gutson at tallertechnologies dot com>
- Date: Thu, 10 Mar 2016 23:24:47 -0500
- Subject: Re: [PING 2][PATCH v3] Add pretty printers for the NPTL lock types
- Authentication-results: sourceware.org; auth=none
- References: <1447768994-5368-1-git-send-email-martin dot galvan at tallertechnologies dot com> <20160209155450 dot GE1904 at devel dot intra dot reserved-bit dot com> <CAOKbPbYPtn5mMpwGGD-HccXnhNz+eymiJ7Xwe_4WOnesYkw5=A at mail dot gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1602091743430 dot 29757 at digraph dot polyomino dot org dot uk> <CAOKbPba5MGw8XCXRSvapfADD1v_0FoVYhUeJUp01YBXyELLMkg at mail dot gmail dot com> <alpine dot DEB dot 2 dot 10 dot 1602101301131 dot 23420 at digraph dot polyomino dot org dot uk> <56BCB9C7 dot 6000100 at redhat dot com> <CAOKbPbZMt+ozv8dPbC8hpZr6yw2d2HcV4OskRP+Pk-i3oYu=nQ at mail dot gmail dot com> <56D5DFE3 dot 5010401 at redhat dot com> <CAOKbPbY_TPXBuFWT_eZCOBKiF-uSWZndAT3cuL3ZvZF+htbCRQ at mail dot gmail dot com> <CAOKbPbY0QW-KvhegDbs3NCuv-hHKyf-peuL1aBon+YTCt2SfEg at mail dot gmail dot com> <CAOKbPbayyOUC16atuMn0ooZCL75FGCHFuNH_wo2PaMjQDgRqeg at mail dot gmail dot com>
On 03/10/2016 03:39 PM, Martin Galvan wrote:
> After dwelling a bit more into the test system, I think I'm beginning
> to understand how the test-wrapper variables work. Correct me if I'm
> wrong but, except for NaCl, most (if not all) the tests should work
> with cross-test-ssh.sh. If that's the case, I think the simplest way
> to do this is to use the gdb that's in the system where the
> cross-glibc runs, and use cross-test-ssh.sh to run my test scripts. If
> required I could check whether Python and gdb actually exist in the
> target, failing with UNSUPPORTED if they don't.
Correct.
You can absolutely do that, return exit code 77 to indicate the test
was UNSUPPORTED.
The alternative is to run the test with a host cross-gdb that talks
to a gdbserver (which you'd have to start as part of the test). It's
certainly easier to just run everything on the target, and that's fine.
> Assuming I'm correct, in that case I shouldn't need to define any
> additional variables. test-wrapper should be enough.
Right.
> I'm about to run a cross make check using cross-test-ssh.sh on a
> Beaglebone Black running Debian; hopefully I can later use it to
> cross-tests my printers.
Sounds good.
--
Cheers,
Carlos.