[Bug general/27367] readelf: invalid loclists data with -ffat-lto-objects

2021-11-04 Thread ldv at sourceware dot org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=27367 --- Comment #5 from Dmitry V. Levin --- Could we have this issue fixed, please? -- You are receiving this mail because: You are on the CC list for the bug.

[Bug tools/27856] eu-elfcompress exit code changed to a error if 'Nothing to do'

2021-05-12 Thread ldv at sourceware dot org via Elfutils-devel
|unassigned at sourceware dot org |ldv at sourceware dot org Resolution|--- |FIXED --- Comment #4 from Dmitry V. Levin --- Fixed by commit 43ac25c2de7ba21fb8f9e4d4db0c01c1408da0b8. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug general/27450] Update Polish translation

2021-03-06 Thread ldv at sourceware dot org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=27450 --- Comment #10 from Dmitry V. Levin --- (In reply to Piotr Drąg from comment #9) > I already included Signed-off-by in the patches. As for POTFILES, I use > intltool-update -m to detect missing files. > > (In reply to Dmitry V. Levin from co

[Bug general/27450] Update Polish translation

2021-03-05 Thread ldv at sourceware dot org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=27450 --- Comment #8 from Dmitry V. Levin --- (In reply to Mark Wielaard from comment #7) > Two questions: > > 1) How should we manage the POTFILES? How did you note the missing files? > Can this be automated somehow? I was using $ git grep -El '\

[Bug general/27450] Update Polish translation

2021-02-21 Thread ldv at sourceware dot org via Elfutils-devel
|NEW CC||ldv at sourceware dot org Last reconfirmed||2021-02-21 --- Comment #4 from Dmitry V. Levin --- (In reply to Piotr Drąg from comment #2) > Created attachment 13238 [details] > Update POTFI

[Bug tools/27351] please add a debugedit binary to elfutils

2021-02-05 Thread ldv at sourceware dot org via Elfutils-devel
https://sourceware.org/bugzilla/show_bug.cgi?id=27351 --- Comment #1 from Dmitry V. Levin --- I second this. The only technical complication I see is that debugedit uses Autotest for testing while the rest of elfutils uses tests driven by Automake. -- You are receiving this mail because: You a

[Bug libdw/26177] eu-unstrip -n -k fails on kernels 4.14-4.19

2020-06-26 Thread ldv at sourceware dot org via Elfutils-devel
|kernels 4.14-4.19 |kernels 4.14-4.19 CC||ldv at sourceware dot org -- You are receiving this mail because: You are on the CC list for the bug.

[Bug libelf/23916] [bisected] elifutils-0.175 broke kernel's objtool (elifutils-0.173 works)

2018-12-02 Thread ldv at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23916 Dmitry V. Levin changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug binutils/23919] bfd doesn't handle ELF compressed data alignment

2018-11-28 Thread ldv at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23919 --- Comment #8 from Dmitry V. Levin --- When we backported these fixes to our 2_31 based branch, we got a surprising regression in gold/testsuite: $ cat gold/testsuite/debug_msg.sh.log Did not find expected error in debug_msg_so.err: debug

[Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in at least 0.173

2018-09-19 Thread ldv at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23673 --- Comment #12 from Dmitry V. Levin --- (In reply to Martin Liska from comment #11) > With the suggested patch I see following in test-suite.log on s390x: [...] > [ 86s] FAIL: run-backtrace-dwarf.sh > [ 86s] >

[Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in at least 0.173

2018-09-19 Thread ldv at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23673 Dmitry V. Levin changed: What|Removed |Added CC||ldv at sourceware dot org

[Bug tools/23673] TEST ./tests/backtrace-dwarf fails on s390x in at least 0.173

2018-09-19 Thread ldv at sourceware dot org
https://sourceware.org/bugzilla/show_bug.cgi?id=23673 --- Comment #8 from Dmitry V. Levin --- If a process is not being traced and PTRACE_TRACEME fails with EPERM, then it must be a kernel issue. -- You are receiving this mail because: You are on the CC list for the bug.