#53 Linux segfault as edge loads
Level entry must have an EPISODE name !
Error occurred near line 22 of DDFLEVL
Error occurred in entry: [MAP01]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 21565)]
0x4022bdf1 in kill () from /lib/libc.so.6
(gdb) bt
#0 0x4022bdf1 in kill () from /lib/libc.so.6
#1 0x400b006d in pthread_kill () from /lib/libpthread.so.0
#2 0x400b05eb in raise () from /lib/libpthread.so.0
#3 0x0804af18 in I_Error(char const*, ...) (error=0x80fd953
"%s")
at linux/i_system.cpp:204
#4 0x080576ce in DDF_Error(char const*, ...) (
err=0x80fcba0 "Level entry must have an EPISODE name
!\n")
at ddf_main.cpp:91
#5 0x08056388 in LevelFinishEntry () at ddf_levl.cpp:256
#6 0x0805856d in DDF_MainReadFile(readinfo_s*)
(readinfo=0xbfffee80)
at ddf_main.cpp:741
#7 0x080564aa in DDF_ReadLevels(void*, int)
(data=0x83b3934, size=16220)
at ddf_levl.cpp:313
#8 0x080d40be in AddFile (filename=0x81f9cc4 "./edge.wad",
allow_ddf=true,
dyn_index=-1) at w_wad.cpp:701
#9 0x080d448c in W_InitMultipleFiles() () at w_wad.cpp:833
#10 0x08060fec in E_EDGEMain() () at e_main.cpp:1480
#11 0x0804a6fe in main (argc=1, argv=0xbffff4d4) at
linux/i_main.cpp:98
#12 0x4021a4a2 in __libc_start_main () from /lib/libc.so.6
Logged In: YES
user_id=98706
DDFLEVL is the wad lump entry for levels.ddf. The error
message "Level entry must have an EPISODE name !"
suggests that in the DDFLEVL lump there is a missing EPISODE
command.
If I omit the EPSIODE line for the MAP01 entry from my
levels.ddf, I get a crash on my windows version of EDGE with
exactly the same message....
Are you loading a custom wad when you start EDGE? If so
then the EPISODE entry could be missing from a DDFLEVL
lump in that wad, so see if you get the error without loading
the custom wad. If you're not loading a custom wad, then
there may be a problem with the copy of the edge.wad that
you have. i.e. the EPSIODE entry may be missing from the
DDFLEVL lump of the edge.wad. In that case try downloading
edge_wad-2.5.zip again and extracting it to your EDGE
directory. If that still doesn't work let me know and I can
perhaps email you a copy of edge.wad
Logged In: NO
I should probably mention that I was using the latest code from cvs,
rather than version 1.27. Does the cvs version need an updated
edge.wad? If so, I think that should be kept on the cvs server too.
I was looking at possibly improving the code, or at least just fiddling
with it. However, if I can't even get the latest code working, I probably
won't even bother.
Logged In: YES
user_id=98706
Hmmm...
Well, unless there has been a change to the ddf parser in the
cvs, you shouldn't need a new edge.wad (for ddf purposes).
If there has been a change to the parser, then it's entirely
possible that an edge.wad has not been done yet, or that the
cvs is not currently useable anyway... the developers are still
working on it, albeit at a reduced rate.
If we assume the cvs is workable, then I would still try either
a freshly downloaded edge.wad, or an alternative ddf folder
(using the command line parameter -ddf <foldername> ). I say
this because the error message you are getting, imho,
indicates a problem with a particular line of the specified ddf
file/lump (and not the first ddf file that loads in, but one of
the later ones, suggesting an error in the file/lump rather than
a problem with the ddf parser).
Other than that I can only suggest speaking to the developer
(who doesn't seem to appear here very often), as he will
know more about whether the cvs is workable and whether
your problem is with that rather than anything else.
Logged In: YES
user_id=11869
I can't duplicate this with the current EDGE.WAD (2.6) or
using the current DDF files (3.7) externally. Therefore I'm
closing this bug.
BTW, it segfaults (rather than shutdown nicely) as an aid to
debugging. Remove the -DDEVELOPERS from the makefile to
change this.
Logged In: NO
I checked edge out from cvs again yesterday (12/15/2003). I
no longer have this problem. Edge starts fine.