From: Mark Wielaard <mark@klomp.org>
To: Di Chen <dichen@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils - failed test (failure) (master)
Date: Mon, 1 Aug 2022 02:09:52 +0200 [thread overview]
Message-ID: <YucZ0L9CL6Wu20gn@wildebeest.org> (raw)
In-Reply-To: <20220731235433.1EFF93857C5C@sourceware.org>
On Sun, Jul 31, 2022 at 11:54:33PM +0000, builder--- via Elfutils-devel wrote:
> A new failure has been detected on builder elfutils-fedora-s390x while building elfutils.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/43/builds/47
>
> Build state: failed test (failure)
> Revision: 369c021c6eedae3665c1dbbaa4fc43afbbb698f4
> Worker: fedora-s390x
> Build Reason: (unknown)
> Blamelist: Di Chen <dichen@redhat.com>
> [...]
> - 7: make check ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#builders/43/builds/47/steps/7/logs/stdio
> - test-suite.log: https://builder.sourceware.org/buildbot/#builders/43/builds/47/steps/7/logs/test-suite_log
So that is in the one little addition I made:
-==3856043== Invalid read of size 1
-==3856043== at 0x484EBE8: memrchr (vg_replace_strmem.c:1012)
-==3856043== by 0x100FEDF: handle_dynamic (readelf.c:1909)
-==3856043== by 0x102061D: print_dynamic (readelf.c:2013)
-==3856043== by 0x102061D: process_elf_file (readelf.c:1034)
-==3856043== by 0x1021FDB: process_dwflmod (readelf.c:818)
-==3856043== by 0x4962BCF: dwfl_getmodules (dwfl_getmodules.c:86)
-==3856043== by 0x100E175: process_file (readelf.c:926)
-==3856043== by 0x1006A75: main (readelf.c:395)
-==3856043== Address 0x56df358 is 24 bytes before a block of size 264 alloc'd
-==3856043== at 0x484C002: calloc (vg_replace_malloc.c:1328)
-==3856043== by 0x4A4EED9: elf_getdata_rawchunk (elf_getdata_rawchunk.c:173)
-==3856043== by 0x1010621: get_dynscn_strtab (readelf.c:4958)
-==3856043== by 0x1010621: handle_dynamic (readelf.c:1884)
-==3856043== by 0x102061D: print_dynamic (readelf.c:2013)
-==3856043== by 0x102061D: process_elf_file (readelf.c:1034)
-==3856043== by 0x1021FDB: process_dwflmod (readelf.c:818)
-==3856043== by 0x4962BCF: dwfl_getmodules (dwfl_getmodules.c:86)
-==3856043== by 0x100E175: process_file (readelf.c:926)
-==3856043== by 0x1006A75: main (readelf.c:395)
I am staring at the code, but don't immediately see which mistake I
made. Maybe I should use d_val instead of d_ptr (but those are both
uint64_t so that shouldn't really matter).
Cheers,
Mark
next prev parent reply other threads:[~2022-08-01 0:09 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 23:54 builder
2022-08-01 0:09 ` Mark Wielaard [this message]
2022-08-01 9:13 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2023-01-14 2:51 builder
2022-12-21 18:22 builder
2022-12-19 23:56 builder
2022-12-12 14:31 builder
2022-11-28 13:30 builder
2022-11-04 22:29 builder
2022-11-03 15:27 builder
2022-11-02 13:39 builder
2022-11-02 14:19 ` Mark Wielaard
2022-11-02 1:15 builder
2022-11-02 12:06 ` Mark Wielaard
2022-11-01 21:28 builder
2022-10-31 13:51 builder
2022-10-27 19:25 builder
2022-10-17 14:59 builder
2022-10-17 9:08 builder
2022-10-17 10:26 ` Mark Wielaard
2022-10-17 11:02 ` Frank Ch. Eigler
2022-10-17 14:09 ` Frank Ch. Eigler
2022-10-16 21:02 builder
2022-10-16 15:47 builder
2022-10-16 16:26 ` Mark Wielaard
2022-10-13 16:51 builder
2022-09-14 19:36 builder
2022-05-28 9:15 builder
2022-05-28 9:35 ` Mark Wielaard
2022-05-28 9:43 ` Mark Wielaard
2022-06-02 15:44 ` Mark Wielaard
2022-05-27 16:02 builder
2022-05-27 22:30 ` Mark Wielaard
2022-05-28 2:34 ` Frank Ch. Eigler
2022-05-28 9:04 ` Mark Wielaard
2022-05-14 15:34 builder
2022-05-14 16:40 ` Mark Wielaard
2022-05-14 14:42 builder
2022-05-04 15:34 builder
2022-05-04 17:44 ` Mark Wielaard
2022-04-23 13:19 builder
2022-04-23 1:19 builder
2022-04-23 1:31 ` Mark Wielaard
2022-04-19 9:05 builder
2022-04-19 9:28 ` 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=YucZ0L9CL6Wu20gn@wildebeest.org \
--to=mark@klomp.org \
--cc=dichen@redhat.com \
--cc=elfutils-devel@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).