Back to the Vavoom Forum Archives


Forum

[Not a Bug][1.33][Debian amd64] Segfault when loading IWAD

Fri, 04 Mar 2011 08:06:17

BondEar

Whenever I try to load any IWAD it gives me a Segmentation Violation. However these IWADS run fine in other engines like PrBoom. Here's an example. I run this command:
vavoom -doom1 -iwaddir ~/wads/doom1/doom1.wad -debug -debug_decorat
Fri, 04 Mar 2011 10:54:27

b0rsuk

In Vavoom, it could be anything <!-- s:-) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":-)" title="Smile" /><!-- s:-) -->. There are no helpful error messages. Maybe we could determine something if you provided more information. What's the name of th
Fri, 04 Mar 2011 12:07:54

Crimson Wizard

[quote="b0rsuk":38m8va5f]In Vavoom, it could be anything <!-- s:-) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":-)" title="Smile" /><!-- s:-) -->. There are no helpful error messages. Isn't the following message helpful? [q
Fri, 04 Mar 2011 13:15:15

b0rsuk

Okay, sorry for that.
Fri, 04 Mar 2011 16:22:02

Firebrand

This crash is odd, seems you are trying to load a shareware IWAD file, right? Do you know which version of IWAD it is?
Fri, 04 Mar 2011 17:26:38

BondEar

It's shareware 1.9. I tried it with Freedoom and Blasphemer and they fail with the same error message. All of these IWADs run in other engines fine though.
Mon, 07 Mar 2011 04:06:43

BondEar

I just got GCC 4.5.2 through my update manager. I tried compiling Vavoom 1.33 with it, but Vavoom still gives me the same error messages.
Mon, 07 Mar 2011 16:06:49

Firebrand

I'll try to load a shareware IWAD ASAP.
Fri, 11 Mar 2011 16:14:03

Firebrand

Well, they work fine for me, both the Freedoom and Doom shareware wads work without crashing. So I don't know what else could trigger the crashes for you.
Fri, 11 Mar 2011 19:13:15

BondEar

Actually I think it might not be loading what I put in -iwaddir. For some reason, no matter what I use for -iwaddir, it starts out with this:
Adding /usr/local/share/vavoom/basev/common/basepak.pk3
adding /usr/local/share/vavoom/doom2&#
Fri, 11 Mar 2011 19:19:08

b0rsuk

[quote="BondEar":33y1sxnz] NOTE: doom2.wad is a symlink to freedoom.wad. That's all it loads. Do you have any idea what's going on with this? Why won't it load what's in -iwaddir? I know the answer. Sor
Fri, 11 Mar 2011 20:43:02

mnk

Tilde expansion is a [u:eygmxalg]shell[/u:eygmxalg] feature, that has nothing to do with "relative paths".
Sat, 12 Mar 2011 00:48:40

Firebrand

I'm closing this as not a bug then <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) -->.
Sat, 12 Mar 2011 03:17:30

BondEar

[quote="b0rsuk":1mtlx2i3]Vavoom doesn't understand relative paths on Linux. You're launching with ~/something, where "~" is basically the same as $HOME, right ? In my case, my username is b0rsukThe freedoom.wad file you included isn't for Doom1 it's for Doom2, to run it, you need to use '-doom2' parameter in the command line
$ vavoom -doom2
Adding /usr/local/share/vavoom/base
Fri, 25 Mar 2011 19:01:53

Firebrand

[quote="BondEar":2xx0aobn][quote="Firebrand":2xx0aobn]The freedoom.wad file you included isn't for Doom1 it's for Doom2, to run it, you need to use '-doom2' parameter in the command line
$ vavoom -doom2

Back to the Vavoom Forum Archives