Ewen> (h=10240K,ib=2048K,ip=100%,mb=6144K,mp=20%) Segmentation fault
Edit driver/Makefile and remove the optimization part (-O2). For extra safety add -fno-strict-aliasing
Hello,
thanks a lot for the reply. I did what you suggested, but I'm afraid I still get a segmentation fault - with the following useless backtrace:
Core was generated by `./poly'. Program terminated with signal 11, Segmentation fault. Cannot access memory at address 0xb7f827e8 #0 0xb7ec73c3 in ?? () (gdb) bt #0 0xb7ec73c3 in ?? () ...
Ewen
On 18 Oct 2005 23:48:48 -0400, Ian Zimmerman itz@buug.org wrote:
Ewen> (h=10240K,ib=2048K,ip=100%,mb=6144K,mp=20%) Segmentation fault
Edit driver/Makefile and remove the optimization part (-O2). For extra safety add -fno-strict-aliasing
Hi, On Tue, Oct 18, 2005 at 06:20:14PM -0200, Ewen Maclean wrote:
Please forgive me if this is a copy of an error that has already been discussed, but I couldn't find a solution in the archives. This is the first time I have tried installing polyml on my debian linux machine which is running a 2.6.13 kernel. I have tried the binaries and compiling from source and everytime I try running polyml I get a segmentation fault. This is what happens:
this is a well known problem on the latest linux kernels. Please try the upcomming 4.1.4 version of polyml from http://www.sf.net/projects/polyml
Achim
Thanks a lot - that worked.
Ewen
this is a well known problem on the latest linux kernels. Please
try the upcomming 4.1.4 version of polyml from http://www.sf.net/projects/polyml
Achim
-
brucker＠spamfence.net -
ewenmaclean＠gmail.com -
itz＠buug.org