After a couple of months off, I've just tried the latest nightly (r3760) with my development pak128.Britain and I get a seg fault on startup:
...
Reading city configuration ...
Reading speedbonus configuration ...
Reading menu configuration ...
Reading object data from pak128-gb/...
Segmentation fault
It works fine with the last nightly I had (r3543). I'm not reporting this as a bug straightaway as it could well be I need to change something in the pak to take account of a recent change in how the exe works, which I've missed in my absence. Can anyone offer any clues?
I can't help with the problem (at the moment - am compiling the latest version of Standard now), but welcome back! Hope that you had a good summer.
Welcome back :)
Please delete settings.xml and try again.
If this does not help: Could you run the game in the debugger gdb? I.e. in a shell write 'gdb ./simutrans-xxx'. Then 'r' as 'run', which starts the program. After the crash type 'bt' as 'backtrace' in the debugger and post the result here.
Ok this is what I get with the debugger:
Loading BDF font 'font/Prop-Latin1.bdf'
Loading BDF font font/Prop-Latin1.bdf with 256 characters
Reading city configuration ...
Reading speedbonus configuration ...
Reading menu configuration ...
Reading object data from pak128-gb/...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7c2d6d0 (LWP 5980)]
0x0804f1b8 in ?? ()
(gdb) bt
#0 0x0804f1b8 in ?? ()
#1 0xbfcf7a18 in ?? ()
#2 0x08079ef9 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
I'm still getting this with r3785 - did the post above help at all?
Debugger output was not that useful. Something weird went wrong.
Does this happen with an official pak128.Britain pakset?
If not could you upload your pakset somewhere? You can send me the download location per PM.
No - it's fine with nightly pak r320. I wonder whether it needs all paks to be made with the latest makeobj - some of the pak files are pretty old... Anyway, I guess that just means I need to play around until I work out what's causing the problem - it's obviously not a general problem with the pak sources being out of date.