Hi,
i tar 1.14-1 GNU tar - tape archiver sagwa:~ cabo$ fink --version Package manager version: 0.20.3 Distribution version: 0.7.0.cvs
My problem:
sagwa:~ cabo$ /sw/bin/gtar Segmentation fault sagwa:~ cabo$
This crash happens before the command line options are even evaluated.
(The same is true for /sw/bin/tar, which I already moved away to keep my mental sanity).
I've tried reinstalling and rebuilding tar already, no change.
More detail below.
Any ideas how to fix this?
Gruesse, Carsten --------------------------------
sagwa:~ cabo$ gdb /sw/bin/gtar
GNU gdb 5.3-20030128 (Apple version gdb-309) (Thu Dec 4 15:41:30 GMT 2003)
[bla bla]
Reading symbols for shared libraries .... done
(gdb) break bindtextdomain
Breakpoint 1 at 0xefeda868: file intl-compat.c, line 156.
(gdb) run
Starting program: /sw/bin/gtar
Temporarily disabling shared library breakpoints: 1
Reading symbols for shared libraries . done
Re-enabling shared library breakpoints: 1
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x8a4ca868 in ?? ()
(gdb) where
#0 0x8a4ca868 in ?? ()
Cannot access memory at address 0x8a4ca868
Cannot access memory at address 0x8a4ca868
#1 0x0001964c in main (argc=1, argv=0xbffffb6c) at tar.c:1497
(gdb) info br
Num Type Disp Enb Address What
1 breakpoint keep y 0xefeda868 in bindtextdomain at intl-compat.c:156
(gdb)
(line 1497 contains the call to bindtextdomain()).
So why does gdb (and probably the shared library code think bindtextdomain is at 0xefeda868 while the code seems to jump to 0x8a4ca868?
------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
