1.Virtual Functions in Shared object not invoked properly by AIX Linker
Compiler used VisualAge C++ Professional / C for AIX Compiler, Version 5 We are getting a strange problem with virtual functions which are not being bound to proper address, but the same code is working on Solaris. The scenario is something like this. I have a shared library (.so) which has a class with all virtual functions in it. In the executable, I am creating an object of that class and invoking its functions. Eg:- Class temp { virtual void func1(); virtual void func2(); virtual void func3(); }; void temp::func1() { func2(); func3(); } void temp::func2() { } void temp::func3() { } In main, I use temp this way main() { temp myobj; myobj.func1(); } func1 is invoked properly and inside it,the very invocation of func2() leads to the core dump with a message like Illegal instruction (illegal opcode) in . at 0x0 ($t15) warning: Unable to access address 0x0 from core (dbx) where warning: Unable to access address 0xfffffffffffffffc from core warning: Unable to access address 0xfffffffffffffffc from core warning: Unable to access address 0xfffffffffffffffc from core warning: Unable to access address 0xfffffffffffffffc from core .() at 0x0 We had analysed the core dump with the registers command and found the IAR register containing the NULL address. If the functions func2 and func3 are changed to non virtual, there is no crash. Though the example shown is a very miniature version of the actual one, I think the problem I am facing is understandable with it. Shared libaries are being build with xlC_r -G option. Linking is done with -brtl and -bdynamic options. Any comments and suggestions are welcome.
2.Virtual Functions in Shared object not invoked properly by AIX Linker Inbox
Compiler used VisualAge C++ Professional / C for AIX Compiler, Version 5 We are getting a strange problem with virtual functions which are not being bound to proper address, but the same code is working on Solaris. The scenario is something like this. I have a shared library (.so) which has a class with all virtual functions in it. In the executable, I am creating an object of that class and invoking its functions. Eg:- Class temp { virtual void func1(); virtual void func2(); virtual void func3(); }; void temp::func1() { func2(); func3(); } void temp::func2() { } void temp::func3() { } In main, I use temp this way main() { temp myobj; myobj.func1(); } func1 is invoked properly and inside it,the very invocation of func2() leads to the core dump with a message like Illegal instruction (illegal opcode) in . at 0x0 ($t15) warning: Unable to access address 0x0 from core (dbx) where warning: Unable to access address 0xfffffffffffffffc from core warning: Unable to access address 0xfffffffffffffffc from core warning: Unable to access address 0xfffffffffffffffc from core warning: Unable to access address 0xfffffffffffffffc from core .() at 0x0 We had analysed the core dump with the registers command and found the IAR register containing the NULL address. If the functions func2 and func3 are changed to non virtual, there is no crash. Though the example shown is a very miniature version of the actual one, I think the problem I am facing is understandable with it. Shared libaries are being build with xlC_r -G option. Linking is done with -brtl and -bdynamic options. Any comments and suggestions are welcome.
3.crontab -e or crontab -l is not functioning properly
Hello Group! I have situation with crontab -e and crontab -l commands not functioning properly on an Utlra 1 running SUN Solaris 5.8 Patch_Level is 13. It was working fine until one of the Windows Admins tried to edit the crontab file through a text editor instead of vi. He overwrote the original files when he saved the changes to the crontab file. So now when you type in the commands <crontab -e> or <crontab -l> you get this error message below: #ld.so.l:crontab: fatal: relocation error: file crontab: symbol audit_crontab_not_allowed: referenced symbol not found. killed # Can anyone shead some light to how I can fix this issue with the crontab command?
4.[uml-devel] [PATCH 3/4] UML - Properly invoke x86_64 system calls
5.[PATCH 3/4] UML - Properly invoke x86_64 system calls
6. invoking ld(1) with -z ld32=arg when arg takes a comma
7. tcsetattr (on serial device) takes effect only at next application startup
Users browsing this forum: No registered users and 31 guest