Per Persson wrote:
Frank Heckenbach wrote: The difference might be due to different compiler options. `-g' seems a likely candidate. If you compile with `-g' on the command line, does it crash as well. If so, you might want to use `--debug-source' to find where in your program it crashes, but in general, debug info generation in GPC is not very stable yet, so I can't promise whether it can be fixed soon.
I tried the -g option with the gpc from the command prompt and the program compiled without problems (and an executable was produced), so I think the problem has to do with RHIDE in some way. The program also compiles from inside rhide in the djgpp version (gpc version 20010623, based on 2.95.3 20010315/djgpp (release)). I then tried to install another binary version (rhide-1.4.9-1.i386.rpm) but the result was the same.
All RHIDE can really do is call GPC with different options (or *perhaps* environment variables, but I don't think so). Try to see which options it uses (don't know if/how this is possible from within RHIDE -- if nothing else helps, you could temporarily install in place of gpc a little script that just dumps its options).
#!/bin/sh { echo "$0 was called with the following arguments:"; echo "$@"; } > /dev/tty
(Under Dos, replace `/dev/tty' by `con' IIRC, though DJGPP might also work with `/dev/tty'.)
Should I try to compile rhide from the sources?
I don't suppose this will make a difference.
Is it tricky?
Maybe. Last time I tried (some years ago) I had some problems -- I think because of changes in the C++ standard. If it's been ported to the current C++ standard meanwhile, I suppose it will be easier.
Frank