[esp-r] Re: prj: segmentation fault
Lukas Swan (Dal)
lswan at dal.ca
Wed Feb 14 22:59:28 GMT 2007
Hi:
I checked both suggestions- 75 and 100 dpi bitmap fonts are installed.
Then I compiled with ---debug support.
I ran the "prj" using the "gdb" program and it said:
(no debugging signals found)
Program received signal SIGSEGV, Segmentation fault.
0x00000000007db4b7 in f_exit ()
Does this mean anything to you Jon?
Thanks
Lukas Swan
_____
From: Jon Hand (clcv10) [mailto:jon at esru.strath.ac.uk]
Sent: February 14, 2007 8:24 AM
To: Lukas Swan ((Dal))
Cc: esp-r list
Subject: Re: [esp-r] prj: segmentation fault
A recent question about ESP-r and 64 bit compiling.....
I have just downloaded and compiled ESP-r on a FedoraCore 6 OS using g77.
It is a dual processor 64bit machine
When complied for GTK it works very well
When compiled for X11, and I run the command "prj" it briefly opens the
project manager window (<<1second) and then says "Segmentation fault" in my
terminal
This occurs for any of the binaries (e.g. "bps").
Any ideas?
I also am running it on a single processor 32bit machine with Fedora Core 6
and the X11 version works fine.
Testing is underway to ensure that ESP-r works on 64-bit computing
platforms.
At this point there are numerical issues with 64-bit environments which
have
yet to be resolved. There is not yet a consensus in the ESP-r development
community
to recommend using ESP-r on 64 bit platforms.
Previous posts have also talked about work underway to prove that the newest
GCC compilers (4.1.1 onwards) pass the validation tests.
It should be possible for someone who has a 64 bit platform to Install
esp-r with debugging on and to run the executable within a debugging
environment
such as gdb or ddd and track down the location where the segementation
falult is happening.
-ESRU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.strath.ac.uk/archives/esp-r/attachments/20070214/8fb25e8c/attachment-0001.html
More information about the esp-r
mailing list