[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/30069] objdump (*-w64-mingw32) does not support the output
From: |
nickc at redhat dot com |
Subject: |
[Bug binutils/30069] objdump (*-w64-mingw32) does not support the output of c++ symbol names for dynamic libraries |
Date: |
Fri, 03 Feb 2023 12:33:31 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=30069
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-02-03
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at sourceware dot org |nickc at redhat dot com
Ever confirmed|0 |1
--- Comment #3 from Nick Clifton <nickc at redhat dot com> ---
Hi Ralf,
OK, what do you think of the uploaded patch ?
If objdump is run with the -p/-x and -C/--demangle options then it will
display:
objdump: Warning: demangling is not supported for symbol names displayed in
private headers
In addition it updates the documentation, so that the description of
objdump's -C option includes a mention of this limitation.
Whilst testing this patch I did find one other problem however. Because some
PE symbols have prefixes the demangler can be confused. For example:
% x86_64-w64-mingw32-objdump --syms --demangle=gnu-v3 libgmpxx-4.dll | grep
_ZN
[131](sec 8)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000000003e8
__imp__ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_appendEPKcy
[134](sec 8)(fl 0x00)(ty 0)(scl 2) (nx 0) 0x00000000000003f0
__imp__ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_mutateEyyPKcy
..etc..
So maybe the warning needs to be extended ?
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.