Page 1 of 1

[unable to reproduce] 1.0.13 - Heretic E1L1

Posted: Sun Jun 11, 2006 0:00
by funduke
Hello!

I found an interesting bug.

I use win2k.
After downloading the latest gzdoom (Version 1.0.13), i had a crash of it in the first level of Heretic (in god mode), when i entered the bridge. Everything freezed, i wasn't able to close the gzdoom program via the taskmanager and had to reboot my computer.

Strange thing is:
This WAD
http://cd.textfiles.com/nopv17/027A/1_6TRON.ZIP
contains E1M1 of heretic in a to doom2 converted version as MAP02.
I experineced exactly the same crash, when i entered that bridge (also in god mode, i don't know, if that matters).

So i think, there must be a problem with that special level in both heretic and doom2 versions.

Greetings
Funduke

Edit:
My computer has 700 mhz CPU and 120 RAM.

Posted: Sun Jun 11, 2006 9:03
by Graf Zahl
What do you mean by 'bridge'? Which part of the level is that?

Posted: Sun Jun 11, 2006 12:47
by Enjay
I just played the entire map twice - making sure I visited every part of it. No problems experienced.

Posted: Sun Jun 11, 2006 13:35
by funduke
Graf Zahl wrote:What do you mean by 'bridge'? Which part of the level is that?
It's in the beginning of the level, when i just walk forward, and come on to that wood, where on the left and the right side is water. It happened in the beginning of that.

Oh, and it's Heretic v. 1.2.

Greetings
Funduke

Posted: Sun Jun 11, 2006 14:03
by Graf Zahl
No problems here as well. Did you build nodes externally with glbsp or something else?

Posted: Sun Jun 11, 2006 22:19
by funduke
Graf Zahl wrote:No problems here as well. Did you build nodes externally with glbsp or something else?
No, i didn't. It's just the original.
I can't reproduce the bug on my own. It just happened by chance in both cases and it apperared weird to me, that the same strange behaviour of the program appeared in both versions of that certain level, but never on any other.
Just in case, that it happens again in the future:
Is there any way to dump a log of my actions and the responses of the software to it (for example the words, that appear in the console and other error messages)? That might make it easier to track down, what leaded to the problem. The normal zdoom error interface didn't appear, because the program was freezed completely.

Greetings
Funduke

Posted: Sun Jun 11, 2006 22:38
by TheDarkArchon
Add "+logfile log.txt" to your command line

Posted: Mon Jun 12, 2006 14:20
by funduke
TheDarkArchon wrote:Add "+logfile log.txt" to your command line
Many thanks!
I'll do that.

Greetings
Funduke