public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org, gdb@sourceware.org
Subject: Re: buildbot vs --enable-targets=all
Date: Tue, 26 Jul 2022 14:55:43 +0200	[thread overview]
Message-ID: <a70b8d7d3b290017ea1117d4a7e160189c633da2.camel@klomp.org> (raw)
In-Reply-To: <Yt/UKr2YvxSu/U0D@squeak.grove.modra.org>

Hi Alan,

On Tue, 2022-07-26 at 21:16 +0930, Alan Modra wrote:
> On Tue, Jul 26, 2022 at 10:54:12AM +0930, Alan Modra wrote:
> > On Mon, Jul 25, 2022 at 02:25:42PM +0200, Mark Wielaard wrote:
> > > On debian-ppc64 and fedora-ppc64le there are the following ld
> > > failures:
> > > https://builder.sourceware.org/buildbot/#builders/86/builds/343
> > > https://builder.sourceware.org/buildbot/#builders/78/builds/382
> > > 
> > > extra lines in dump.out starting with "^    40: 0000002c     0
> > > TLS     GLOBAL DEFAULT    9 ie0$"
> > > EOF from /var/lib/buildbot/workers/wildebeest/binutils-debian-
> > > ppc64/binutils-gdb/ld/testsuite/ld-powerpc/tlsexe32.r
> > > FAIL: TLS32 dynamic exec
> > [...]
> Oh, you tricked me.  It's not just a single "extra line in.." but a
> bunch of differences then finally that one.

Apologies, I didn't mean to deceive. Just copy/pasted not enough
context.

The full logs files can be found in the bunsendb (see the upload bunsen
step):
https://builder.sourceware.org/testrun/b2ea62b46f245693bf32bdfdabedf95cdc31bd4f

The webwidget has a dejagnu parse view:
https://builder.sourceware.org/testrun/b2ea62b46f245693bf32bdfdabedf95cdc31bd4f?focus=dgsummary

Which you can then use to get at the specific part of the .log file for
an .exp per test:
https://builder.sourceware.org/testrun/b2ea62b46f245693bf32bdfdabedf95cdc31bd4f?dgexpfile=ld-powerpc%2Fpowerpc.exp

In this case:
https://builder.sourceware.org/testrun/b2ea62b46f245693bf32bdfdabedf95cdc31bd4f?filename=ld%2Fld.log&fileline=53358&linewindow=20#line53358

> So for some reason there is an empty .data section, putting all the
> rest of the dump off by one.
> 
> regexp_diff match failure
> regexp "^ +\[[ 0-9]+\] \.symtab +SYMTAB +.*$"
> line   "  [13] .data             PROGBITS        01810398 000398
> 000000 00  WA  0   0  1"
> regexp_diff match failure
> regexp "^ +\[[ 0-9]+\] \.strtab +STRTAB +.*$"
> line   "  [14] .symtab           SYMTAB          00000000 000398
> 000290 10     15  26  4"
> regexp_diff match failure

Thanks. I don't know where that is coming from. It is curious that it
happens on both debian-ppc64 and fedora-ppc64le which are somewhat
different environments.

Cheers,

Mark

  parent reply	other threads:[~2022-07-26 12:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 12:25 Mark Wielaard
2022-07-26  1:24 ` Alan Modra
2022-07-26 11:46   ` Alan Modra
2022-07-26 12:43     ` Alan Modra
2022-07-26 12:55     ` Mark Wielaard [this message]
2022-07-26  1:59 ` Jeffrey Walton
2022-08-03 10:38   ` Mark Wielaard
2022-08-03 10:56     ` Andreas Schwab
2022-08-03 11:35     ` Luis Machado
2022-08-03 11:49       ` Mark Wielaard
2022-08-03 11:54         ` Luis Machado
2022-08-03 11:57           ` 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=a70b8d7d3b290017ea1117d4a7e160189c633da2.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    /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).