TJ
2010-Apr-03 08:03 UTC
[Libguestfs] hivex: Exported foreign symbols in libhivex.so.0.0.0
The symbols file generated in the Debian package to aid the package maintainer automatically detect future changes shows internal library and helper function names, whereas it should only be exporting hivex_* function names. This page may help with this: http://gcc.gnu.org/wiki/Visibility Symbols: asnprintf at Base 1.2.1 c_isalnum at Base 1.2.1 c_isalpha at Base 1.2.1 c_isascii at Base 1.2.1 c_isblank at Base 1.2.1 c_iscntrl at Base 1.2.1 c_isdigit at Base 1.2.1 c_isgraph at Base 1.2.1 c_islower at Base 1.2.1 c_isprint at Base 1.2.1 c_ispunct at Base 1.2.1 c_isspace at Base 1.2.1 c_isupper at Base 1.2.1 c_isxdigit at Base 1.2.1 c_tolower at Base 1.2.1 c_toupper at Base 1.2.1 exit_failure at Base 1.2.1 full_read at Base 1.2.1 full_write at Base 1.2.1 printf_fetchargs at Base 1.2.1 printf_parse at Base 1.2.1 program_name at Base 1.2.1 safe_read at Base 1.2.1 safe_write at Base 1.2.1 set_program_name at Base 1.2.1 vasnprintf at Base 1.2.1 xstrtol at Base 1.2.1 xstrtol_fatal at Base 1.2.1 xstrtoll at Base 1.2.1 xstrtoul at Base 1.2.1 xstrtoull at Base 1.2.1
Richard W.M. Jones
2010-Apr-03 08:28 UTC
[Libguestfs] hivex: Exported foreign symbols in libhivex.so.0.0.0
On Sat, Apr 03, 2010 at 09:03:16AM +0100, TJ wrote:> The symbols file generated in the Debian package to aid the package > maintainer automatically detect future changes shows internal library > and helper function names, whereas it should only be exporting hivex_* > function names. This page may help with this:Yup this is a bug too. In libguestfs we control symbol visibility with a linker script. We need to port this over to hivex too. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones New in Fedora 11: Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 70 libraries supprt'd http://fedoraproject.org/wiki/MinGW http://www.annexia.org/fedora_mingw
Possibly Parallel Threads
- Re: [libhivex] Undefined behavior when accessing invalid (too small) registry hives
- Re: [libhivex] Undefined behavior when accessing invalid (too small) registry hives
- Re: [libhivex] Memory leak in hivex_node_delete_child?
- Re: [libhivex] Memory leak in hivex_node_delete_child?
- [PATCH] Mac OS X: Link iconv in libhivex