See whether booting the machine with noexec=off on the boot command
line in /boot/grub/menu.lst makes a difference.
Regards
-- Bhaskar
ks dot bhaskar at fnis dot com <-- send e-mail here
On Jan 7, 1:38 am, dip...@[EMAIL PROTECTED]
wrote:
> We try to run GT.M on Linux (Suse/redhat) but with CPU Intel Quad Core
> Xeon E5310 and there is no success, on Intel Xeon 5110, Dual Core
> Processor we have no problem, the problem is only on CPU with Quad
> Core, we try some OS, SLES 10, Redhat 4 and Centos 4.
>
> We run the mumps command, compiled with debug information in debugger,
> and here's the stack information:
>
> (gdb) run -direct
>
> Starting program: /cav/gtm/mumps -direct
>
> Program received signal SIGSEGV, Segmentation fault.
>
> 0x08053470 in ?? ()
>
> (gdb) where
>
> #0 0x08053470 in ?? ()
>
> #1 0xb7d3c088 in __JCR_LIST__ () from /cav/gtm/libgtmshr.so
>
> #2 0xb7f0acc0 in _dl_argv_internal () from /lib/ld-linux.so.2
>
> #3 0x00000000 in ?? ()
>
> (gdb) continue
>
> Continuing.
>
> %GTM-F-KILLBYSIGSINFO1, GT.M process 12496 has been killed by a signal
> 11 at address 0x08053470 (vaddr 0x08053470)
>
> %GTM-F-SIGACCERR, Signal was caused by invalid permissions for mapped
> object
|
