Re: [PATCH] tests: run-lfs-symbols.sh needs gawk

[Mark Wielaard]

Hi Sam,

On Thu, 2023-07-20 at 00:16 +0100, Sam James via Elfutils-devel wrote:
> With awk=mawk, I get:
> ```
> FAIL: run-lfs-symbols.sh
> 
> 
> First sanity-check that LFS detection works.
> checking ./testfile-nolfs
> awk: line 3: syntax error at or near /
> FAIL run-lfs-symbols.sh (exit status: 2)
> ```
> 
>   * tests/run-lfs-symbols.sh: Call 'gawk' instead of 'awk'.

Thanks. We already require gawk for known-dwarf.awk, check for it in
configure and use it for the coverage generation.

Pushed,

Mark

☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)

[builder--- via Elfutils-devel]

A new failure has been detected on builder elfutils-centos-x86_64 while 
building elfutils.

Full details are available at:
https://builder.sourceware.org/buildbot/#builders/39/builds/212

Build state: failed test (failure)
Revision: a78fc84d013f925c4bf8ab65eee123bc86fe8b39
Worker: centos-x86_64
Build Reason: (unknown)
Blamelist: Sam James 

Steps:

- 0: worker_preparation ( success )

- 1: set package name ( success )

- 2: git checkout ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/2/logs/stdio

- 3: autoreconf ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/3/logs/stdio

- 4: configure ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/4/logs/stdio
- config.log: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/4/logs/config_log

- 5: get version ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/5/logs/stdio
- property changes: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/5/logs/property_changes

- 6: make ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/6/logs/stdio
- warnings (2): 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/6/logs/warnings__2_

- 7: make check ( failure )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/7/logs/stdio
- test-suite.log: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/7/logs/test-suite_log

- 8: prep ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/8/logs/stdio

- 9: build bunsen.cpio.gz ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/9/logs/stdio

- 10: fetch bunsen.cpio.gz ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/10/logs/stdio

- 11: unpack bunsen.cpio.gz ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/11/logs/stdio

- 12: pass .bunsen.source.gitname ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/12/logs/stdio

- 13: pass .bunsen.source.gitdescribe ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/13/logs/stdio

- 14: pass .bunsen.source.gitbranch ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/14/logs/stdio

- 15: pass .bunsen.source.gitrepo ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/15/logs/stdio

- 16: upload to bunsen ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/16/logs/stdio

- 17: clean up ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/17/logs/stdio

- 18: make distclean ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/18/logs/stdio

A new failure has been detected on builder elfutils-debian-ppc64 while building 
elfutils.

Full details are available at:
https://builder.sourceware.org/buildbot/#builders/63/builds/212

Build state: failed test (failure)
Revision: a78fc84d013f925c4bf8ab65eee123bc86fe8b39
Worker: debian-ppc64
Build Reason: (unknown)
Blamelist: Sam James 

Steps:

- 0: worker_preparation ( success )

- 1: set package name ( success )

- 2: git checkout ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/2/logs/stdio

- 3: autoreconf ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/3/logs/stdio

- 4: configure ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/4/logs/stdio
- config.log: 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/4/logs/config_log

- 5: get version ( success )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/5/logs/stdio
- property changes: 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/5/logs/property_changes

- 6: make ( warnings )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/6/logs/stdio
- warnings (3): 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/6/logs/warnings__3_

- 7: make check ( failure )
Logs:
- stdio: 
https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/7/l

Re: ☠ Buildbot (Sourceware): elfutils - failed test (failure) (master)

[Mark Wielaard]

Hi Sam,

I think only the last one can really be said to be "your issue".

On Thu, 2023-07-20 at 11:37 +, builder--- via Elfutils-devel wrote:
> A new failure has been detected on builder elfutils-centos-x86_64 while 
> building elfutils.
> 
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/39/builds/212
> 
> Build state: failed test (failure)
> Revision: a78fc84d013f925c4bf8ab65eee123bc86fe8b39
> Worker: centos-x86_64
> Build Reason: (unknown)
> Blamelist: Sam James 
> 
> - 7: make check ( failure )
> Logs:
> - stdio: 
> https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/7/logs/stdio
> - test-suite.log: 
> https://builder.sourceware.org/buildbot/#builders/39/builds/212/steps/7/logs/test-suite_log

This is odd. Certainly not caused by your patch:

FAIL: run-backtrace-native-core.sh
dwfl_thread_getframes: no matching address range
backtrace: backtrace.c:81: callback_verify: Assertion `seen_main'
failed.

This is a centos7 box/kernel. We have seen this before, but not
recently. It might just be a "buggy" core file generated.

> A new failure has been detected on builder elfutils-debian-ppc64 while 
> building elfutils.
> 
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/63/builds/212
> 
> Build state: failed test (failure)
> Revision: a78fc84d013f925c4bf8ab65eee123bc86fe8b39
> Worker: debian-ppc64
> Build Reason: (unknown)
> Blamelist: Sam James 
> buildbot/#builders/63/builds/212/steps/6/logs/warnings__3_
> 
> - 7: make check ( failure )
> Logs:
> - stdio: 
> https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/7/logs/stdio
> - test-suite.log: 
> https://builder.sourceware.org/buildbot/#builders/63/builds/212/steps/7/logs/test-suite_log
> 
> A new failure has been detected on builder elfutils-debian-testing-x86_64 
> while building elfutils.
> 
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/145/builds/172
> 
> Build state: failed test (failure) test (failure)
> Revision: a78fc84d013f925c4bf8ab65eee123bc86fe8b39
> Worker: bb1-1
> Build Reason: (unknown)
> Blamelist: Sam James 
> 
> - 7: make check ( failure )
> Logs:
> - stdio: 
> https://builder.sourceware.org/buildbot/#builders/145/builds/172/steps/7/logs/stdio
> - test-suite.log: 
> https://builder.sourceware.org/buildbot/#builders/145/builds/172/steps/7/logs/test-suite_log

These two builder are both running debian testing, which picked up a
bad binutils:
https://inbox.sourceware.org/binutils/20230713215808.ga11...@gnu.wildebeest.org/
Hopefully this gets resolved soon with a newer binutils snapshot.

> A build exception has been detected on builder elfutils-gentoo-sparc while 
> building elfutils.
> 
> Full details are available at:
> https://builder.sourceware.org/buildbot/#builders/225/builds/84
> 
> Build state: exception update (exception)
> Revision: (unknown)
> Worker: gentoo-sparc
> Build Reason: (unknown)
> Blamelist: Sam James 
> 
> Steps:
> 
> - 0: worker_preparation ( success )
> 
> - 1: set package name ( success )
> 
> - 2: git checkout ( exception )
> Logs:
> - stdio: 
> https://builder.sourceware.org/buildbot/#builders/225/builds/84/steps/2/logs/stdio
> - err.text: 
> https://builder.sourceware.org/buildbot/#builders/225/builds/84/steps/2/logs/err_text
> - err.html: 
> https://builder.sourceware.org/buildbot/#builders/225/builds/84/steps/2/logs/err_html
> 

This is your buildbot builder. Please kick it! :)

Cheers,

Mark

eu-strip on .rustc section produce error information

[chenziyang (C) via Elfutils-devel]

Hi elfutils maintainers

I am running 'rpmbuild -ba sysmaster.spec', and produce following error info:
eu-strip: Cannot remove symbol [742] from allocated symbol table [3]

This error is caused by strip_to_debug() function in /usr/bin/find-debuginfo.sh 
which is triggered by rpm-build
[cid:image003.png@01D9BB4F.19E5EE90]

Steps to Reproduce:
eu-strip -R .rustc libtarget_1.so
Actual result:
eu-strip: Cannot remove symbol [742] from allocated symbol table [3]

OR
eu-strip -remove-comment libtarget.so.debug1 libtarget_1.so
Actual result: eu-strip: Cannot remove symbol [742] from allocated symbol table 
[3]

Expected:
eu-strip runs without error info

I am wondering is this an error in strip.c? Because from 
1380961 Mark said 'The 
.rustc section is a non-allocated section' and the comment in strip.c said 
'Removing a real symbol from an allocated symbol table is hard and probably a 
mistake'. There seems to be a conflict.

Please let me know if you need any further information or if there is anything 
else I can do to help. I appreciate your time and look forward to hearing back 
from you soon.

Best regards,
Ziyang

Re: eu-strip on .rustc section produce error information

[Mark Wielaard]

Hi Ziyang,

On Thu, 2023-07-20 at 13:14 +, chenziyang (C) via Elfutils-devel
wrote:
> Hi elfutils maintainers
> 
> I am running 'rpmbuild -ba sysmaster.spec', and produce following error info:
> eu-strip: Cannot remove symbol [742] from allocated symbol table [3]
> 
> This error is caused by strip_to_debug() function in 
> /usr/bin/find-debuginfo.sh which is triggered by rpm-build
> [cid:image003.png@01D9BB4F.19E5EE90]
> 
> Steps to Reproduce:
> eu-strip -R .rustc libtarget_1.so
> Actual result:
> eu-strip: Cannot remove symbol [742] from allocated symbol table [3]
> 
> OR
> eu-strip -remove-comment libtarget.so.debug1 libtarget_1.so
> Actual result: eu-strip: Cannot remove symbol [742] from allocated symbol 
> table [3]

Would you be able to show the sections and symbols for libtarget_1.so.
Specifically what symbol table section 3 is and what 742th symbol in
that table is? And does libtarget_1.so actually contain a .rustc
section?

Thanks,

Mark