https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #34 from Lev Veyde ---
Pushed a new 1-test-new-5.15.92.txt, as the previous one was taken against
a different linux image, thus introducing false differences.
--
You are receiving this mail because:
You are on the CC list for
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
Lev Veyde changed:
What|Removed |Added
Attachment #14711|0 |1
is obsolete|
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #32 from Lev Veyde ---
Opened GCC BZ#108905 - https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108905
regarding the issue of the wrong DWARF information.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #31 from Lev Veyde ---
I verified that the patch fixes a lot of cases, including the ones that haven't
been noticed initially (these can be easily spotted by comparing 1-test.txt
to 1-test-new.txt).
I would like to thank N
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #30 from Lev Veyde ---
Created attachment 14711
--> https://sourceware.org/bugzilla/attachment.cgi?id=14711&action=edit
This is the output from the latest addr2line utility, built from master
(d273049e140ef324be2b018e235ae0ba8021
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #25 from Lev Veyde ---
Created attachment 14708
--> https://sourceware.org/bugzilla/attachment.cgi?id=14708&action=edit
This the output from addr2line-testing program against addr2line containing
Nick's patch
--
You are receivi
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #24 from Lev Veyde ---
So, as discussed it with Nick it's quite tricky situation.
Some of the affected symbols don't exist in any of the source code files, and
probably are generated using macro or some other construct, but a simi
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #23 from Lev Veyde ---
To avoid the possibility that the issue is caused by corrupted binary, I've
recompiled a different version of Linux kernel, 5.15.95, and ran tests against
it as well:
$ llvm-addr2line -fie vmlinux 0xfff
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #22 from Lev Veyde ---
Created attachment 14707
--> https://sourceware.org/bugzilla/attachment.cgi?id=14707&action=edit
This is the test against llvm-addr2line utility, to compare the outputs
--
You are receiving this mail beca
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #21 from Lev Veyde ---
It seems to also depend on a tool.
$ llvm-addr2line -v
llvm-addr2line
LLVM (http://llvm.org/):
LLVM version 14.0.6
Optimized build.
Default target: x86_64-redhat-linux-gnu
Host CPU: skylake
$ llvm-a
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #18 from Lev Veyde ---
OK, compiling a custom version of addr2line with that patch, will update
regarding the results.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #14 from Lev Veyde ---
The latest results as far as the corrupted results are concerned are:
The results seems to be:
symbol#request# (OK) request# (NOT OK)
47620-47627(<= 3652 OK) (>= 3961 NOK)
48021-4802
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #13 from Lev Veyde ---
This is what I get from valgrind:
==23051== 1,196 bytes in 19 blocks are definitely lost in loss record 1 of 3
==23051==at 0x4C2B067: malloc (vg_replace_malloc.c:380)
==23051==by 0x5624B89: strdup (i
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #12 from Lev Veyde ---
(In reply to Nick Clifton from comment #11)
> (In reply to Lev Veyde from comment #0)
> Hi Lev,
>
> > It seems that after a few thousands of results (normally over 3000-4000) the
> > addr2line in pipe mode (
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #10 from Lev Veyde ---
Created attachment 14700
--> https://sourceware.org/bugzilla/attachment.cgi?id=14700&action=edit
1314 requests at most at a time (for a running process)
This seems to return good results.
Using 4000 reque
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #9 from Lev Veyde ---
Created attachment 14699
--> https://sourceware.org/bugzilla/attachment.cgi?id=14699&action=edit
1351 requests at most at a time (for a running process)
48618
0x82e21f2d : int3_magic
This seems to
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #8 from Lev Veyde ---
Created attachment 14698
--> https://sourceware.org/bugzilla/attachment.cgi?id=14698&action=edit
1 requests at most at a time (for a running process)
--
You are receiving this mail because:
You are on
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #7 from Lev Veyde ---
Created attachment 14697
--> https://sourceware.org/bugzilla/attachment.cgi?id=14697&action=edit
5000 requests at most at a time (for a running process)
Bad result at 48618
--
You are receiving this mail
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #6 from Lev Veyde ---
Created attachment 14696
--> https://sourceware.org/bugzilla/attachment.cgi?id=14696&action=edit
4002 requests at most at a time (for a running process)
This one also produces some bad results. Can be teste
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #5 from Lev Veyde ---
Created attachment 14695
--> https://sourceware.org/bugzilla/attachment.cgi?id=14695&action=edit
3431 requests at most at a time (for a running process)
This one gives bad results, can be compared with 3202
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #4 from Lev Veyde ---
Created attachment 14694
--> https://sourceware.org/bugzilla/attachment.cgi?id=14694&action=edit
3202 requests at most at a time
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #3 from Lev Veyde ---
Created attachment 14693
--> https://sourceware.org/bugzilla/attachment.cgi?id=14693&action=edit
4000 requests at most at a time
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #2 from Lev Veyde ---
Also tested it with addr2line version 2.30-117.el8
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30150
--- Comment #1 from Lev Veyde ---
The issue was tested with several addr2line versions, including:
2.27-44.base.el7_9.1
2.36.1-1.el7.2
2.40.50.20230219
--
You are receiving this mail because:
You are on the CC list for the bug.
Severity: normal
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: lveyde at gmail dot com
Target Milestone: ---
It seems that after a few thousands of results (normally over 3000-4000) the
addr2line in pipe mode (with
25 matches
Mail list logo
