Segmentation fault after compiling on CentOS

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download pforth24_090220.zip
2. unzip file
3. cd build/unix
4. make all

Here is the end of the make:

cd /home/jsissom/pforth/pforth_v24/fth;
/home/jsissom/pforth/pforth_v24/fth/pforth -i system.fth ; mv pfdicdat.h
/home/jsissom/pforth/pforth_v24/csrc/pfdicdat.h
PForth V24-LE, built Oct 14 2009 23:05:10
Including: system.fth
/bin/sh: line 1:  5249 Segmentation fault     
/home/jsissom/pforth/pforth_v24/fth/pforth -i system.fth
mv: cannot stat `pfdicdat.h': No such file or directory
make: *** [/home/jsissom/pforth/pforth_v24/csrc/pfdicdat.h] Error 1
[jsissom@localhost unix]$ 

If I go into the fth folder and run pforth -i system.fth, I get this:

[jsissom@localhost fth]$ ./pforth -i system.fth 
PForth V24-LE, built Oct 14 2009 23:05:10
Including: system.fth
Segmentation fault
[jsissom@localhost fth]$ 

This is running Centos 5.3 32 bit under vmware fusion.

Any ideas?
Thanks

Original issue reported on code.google.com by jsis...@gmail.com on 15 Oct 2009 at 5:34

[GoogleCodeExporter]

Not enough information.
Rebuild with debug symbols, reproduce problem and provide backtrace.

Original comment by a...@netbsd.org on 20 Aug 2010 at 11:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It is always good to check the most recent version rather than playing with old 
one.

Original comment by a...@netbsd.org on 23 Aug 2010 at 9:52

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[jsissom@jaguar fth]$ gdb
GNU gdb Fedora (6.8-37.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
(gdb) file pforth
Reading symbols from /home/jsissom/pforth_v24/fth/pforth...done.
(gdb) run -i system.fth
Starting program: /home/jsissom/pforth_v24/fth/pforth -i system.fth
PForth V24-LE, built Aug 23 2010 09:05:35
Including: system.fth

Program received signal SIGSEGV, Segmentation fault.
0x0000000000403cce in pfCatch ()
(gdb) backtrace
#0  0x0000000000403cce in pfCatch ()
#1  0x0000000000401b9f in ffInterpret ()
    at /home/jsissom/pforth_v24/csrc/pfcompil.c:763
#2  0x0000000000401ce7 in ffOuterInterpreterLoop ()
    at /home/jsissom/pforth_v24/csrc/pfcompil.c:918
#3  0x0000000000401d1d in ffIncludeFile (InputFile=<value optimized out>)
    at /home/jsissom/pforth_v24/csrc/pfcompil.c:941
#4  0x0000000000403538 in pfIncludeFile (FileName=0x7fff300c2b2c "system.fth")
    at /home/jsissom/pforth_v24/csrc/pf_core.c:374
#5  0x0000000000403afa in pfDoForth (DicName=0x0, 
    SourceName=0x7fff300c2b2c "system.fth", IfInit=<value optimized out>)
    at /home/jsissom/pforth_v24/csrc/pf_core.c:534
#6  0x0000000000406388 in main ()
(gdb) 

Original comment by jsis...@gmail.com on 23 Aug 2010 at 1:08

[GoogleCodeExporter]

V24 doesn't support 64-bit platforms. Use the recent version.

Original comment by a...@netbsd.org on 23 Aug 2010 at 2:04

[GoogleCodeExporter]

V24 is the most recent release on the web site.

Original comment by jsis...@gmail.com on 23 Aug 2010 at 2:08

[GoogleCodeExporter]

Recent version is V26, get it from VCS.

Original comment by a...@netbsd.org on 23 Aug 2010 at 2:41

[GoogleCodeExporter]

There are no branches or tags in the svn repository.  How do I get V26?

Original comment by jsis...@gmail.com on 23 Aug 2010 at 2:56

[GoogleCodeExporter]

From the trunk.

Original comment by a...@netbsd.org on 23 Aug 2010 at 3:33

[GoogleCodeExporter]

How can you guarantee that the trunk will always work properly as developers 
check in their code?  Also, how can you guarantee that trunk is always V26?  At 
some point it won't be anymore.

Wouldn't it be better to say that 64-bit support doesn't exist and put that on 
the web page until version 26 is actually ready and released and the web site 
updated?

Original comment by jsis...@gmail.com on 23 Aug 2010 at 3:47

[GoogleCodeExporter]

No, it wouldn't because pForth supports 64-bit platforms since V26.
You could have figured the revision already instead of writing pointless 
complains.

As such this PR is useless since the issue was fixed. 
I'm not interested in returning to it again unless you find problem in recent 
version.

Original comment by a...@netbsd.org on 24 Aug 2010 at 8:15

[GoogleCodeExporter]

Thank you for your help and your very professional attitude.  You are a credit 
to open source and attitudes like this are what keeps commercial software 
companies in business.

I'm glad that when I followed the instructions posted for gforth, it worked 
correctly and I didn't have to check with someone to find the undocumented 
secrets to making it work.

I too am completely not interested in your comments.

Original comment by jsis...@gmail.com on 24 Aug 2010 at 11:54

[GoogleCodeExporter]

You didn't hire me to help you.

Original comment by a...@netbsd.org on 24 Aug 2010 at 3:34

[GoogleCodeExporter]

To asau, please be nice.

To jsissom, I'm sorry for the comments here from our volunteers.

The fixes for 64-bit are in SVN. They have not been released yet because we are 
still making a few tweaks and doing some testing. Someone reported some minor 
issues yesterday that we will fix. We hope to prepare a release soon.

Some people prefer to work with the latest code from SVN. Some prefer to wait 
for a stable release. You are welcome to do either. If you don't get a chance 
to test the mods then I will fire up my CentOS and give it a try.

And yes, gforth is a great full featured Forth. It is probably the best choice 
for desktop development. PForth is a small portable Forth that was designed for 
testing embedded systems that do not have an OS. They each have their place.

Original comment by burkp...@gmail.com on 24 Aug 2010 at 4:12

• Changed state: Fixed