Trouble with getopt_long_only
Hi!
I run fairly bleeding edge potato box with libc6 2.1.2-2 installed.
Both my Acrobat reader (acroread 4.0-1) and Netscape (netscape 4.61-21)
will fail. I did a quick gdb session on both just to find a common denominator:
For Netscape:
heaven:~> gdb netscape
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-pc-linux-gnu"...
(no debugging symbols found)...
(gdb) run
Starting program: /usr/local/netscape/netscape
(no debugging symbols found)...
...
Program received signal SIGSEGV, Segmentation fault.
0x402fc4e4 in getopt_long_only () from /lib/libc.so.6
(gdb) backtrace
#0 0x402fc4e4 in getopt_long_only () from /lib/libc.so.6
#1 0x4028c115 in signgaml () from /lib/libc.so.6
#2 0x4028c184 in signgaml () from /lib/libc.so.6
#3 0x40002205 in _dl_boot () from /lib/ld-linux.so.1
(gdb)
For Acroread:
bash-2.02$ gdb $ACRO_EXEC_CMD
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-pc-linux-gnu"...
(no debugging symbols found)...
(gdb) run
Starting program: /usr/lib/Acrobat4/Reader/intellinux/bin/acroread
(no debugging symbols found)...
...
Program received signal SIGSEGV, Segmentation fault.
0x408254e4 in getopt_long_only () from /lib/libc.so.6
(gdb) backtrace
#0 0x408254e4 in getopt_long_only () from /lib/libc.so.6
#1 0x407b5115 in _IcePaAuthDataEntries () from /lib/libc.so.6
#2 0x407b5184 in _IcePaAuthDataEntries () from /lib/libc.so.6
#3 0x40002205 in _dl_boot () from /lib/ld-linux.so.1
(gdb)
They both get there in diffrent ways as you can see, but they fail at
presicely the same place (they are just loaded into diffrent offsets).
Anyway, is this a know bug?
How does we solve this?
Cheers,
Magnus
Reply to: