Re: compiling the 64 bit libdar in AIX 5.3 platform

Thomas Jacob <[email protected]> Mon, 26 Jan 2009 15:55:09 +0100
Newsgroups gmane.comp.sysutils.backup.dar.libdar
Message-ID <[email protected]>
On Sun, 2009-01-25 at 23:21 +0530, Sivakumar Selvam wrote:
> 
> I ran through gdb and got the following output. 
>  
> (gdb) r
> Starting
> program: /usr/sony/iTRx/siva/64bit/dec26/dar-2.3.6/src/dar_suite/.libs/dar
> Program received signal SIGILL, Illegal instruction.
> 0x0000000000000000 in ?? ()
> (gdb) bt
> #0  0x0000000000000000 in ?? ()
> #1  0x09000000011a638c in reg_frame ()
> from /usr/sony/iTRx/siva/64bit/dec26/dar-2..3.6/src/libdar/.libs/libdar.a(libdar.so.4)
> #2  0x09000000011a6490 in _GLOBAL__FI_libdar_so ()
> 
> from /usr/sony/iTRx/siva/64bit/dec26/dar-2.3.6/src/libdar/.libs/libdar.a(libdar.so.4)
> #3  0x09fffffff0001bd4 in mod_init1 () from /usr/ccs/bin/usla64
> #4  0x09fffffff000290c in usl_init_mods () from /usr/ccs/bin/usla64
> #5  0x09fffffff000280c in usl_exec_init_mods ()
> from /usr/ccs/bin/usla64
> #6  0x000000010000029c in __start ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> (gdb)

Sorry but I have not clue about compiling & linking stuff under AIX, all
I can see from this backtrace is that the segfault seems to occur before
any libdar code is called so it's probably a compilation/linking issue.





------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword