R'n'D crash

[Sascha]

Hi there,
I have a big problem:
I created new graphics for the
exit door, everything works, but
when I enter the exit
R'n'D crashs.
Why?
The graphics were there,
but why R'nD crashed

[Martijn]

hi,
I think that you should put the content of stderr.txt (see main directory of RnD), so that Holger or someone else knows what's wrong here.

[Daniel H.]

Most likely, there is a problem in the graphics file with exit.closing

[Holger]

This sounds interesting...

> Most likely, there is a problem in the graphics file with exit.closing

I would also think of something like that -- but usually the program bails out directly after starting then, not in the game itself! :-o

> I think that you should put the content of stderr.txt (see main directory of
> RnD), so that Holger or someone else knows what's wrong here.

Yep. I'm curious if this is a "real" crash, or if the program stops with an error message here. For me, it sounds like a real crash here. :-o

In any case: Sascha, could you please zip that level set completely with all graphics and send it to me by mail? I would like to try to reproduce this problem inside a debugger (if it's a real crash).

[Daniel H.]

but usually the program bails out directly after starting then, not in the game itself! :-o

Well, if you make a mistake like this:

Code: Select all

exit.closing.frames: 0

Then the program will not complain until it tries to show exit.closing. I've had this problem before with accidentally setting the frames setting to 0 on custom elements. The moment you try to 1) view the 32x32 CE in the actual level (not the creator) or 2) press the '?' button with that element selected in the creator (which shows the 32x32 graphic), then the game would instantly crash.

I don't believe that that particular bug leaves any clue in stderr.txt as to what happend.

[Holger]

> Well, if you make a mistake like this:
[...]
> then the game would instantly crash.

*AAARGH*

> I don't believe that that particular bug leaves any clue in stderr.txt as to
> what happend.

That's right, unfortunately -- as with every crash bug, you only get that "SDL parachute deployed" message in "stderr.txt". (In this case, it wasn't a "Segmentation Fault" style crash, but a "Floating Point Exception" crash, indicating that there might have been a division by zero, indicating that some value was zero that should not be zero, but this does not make any difference to the normal user, of course.)

I was 100% sure that I would check and set all ".frames: 0" values to "1", but this was only the case for ".delay: 0" cases (which is also not allowed, but less obvious).

Daniel, thanks a lot for reporting this really nasty bug -- it will be fixed in 3.2.0!

Sascha, could you please check if this was the problem in your case, or if there is another problem that (maybe) caused the crash?

[Daniel H.]

*AAARGH*
Daniel, thanks a lot for reporting this really nasty bug -- it will be fixed in 3.2.0!

You're welcome!

I didn't mention it earlier because I didn't think that it was a big deal. I was just out of my mind one day, settings all the frames values to zero when I meant one...

But with delay, I guess this would be a bigger problem, because more people would probably notice it.

[Sascha]

Sascha, could you please check if this was the problem in your case, or if there is another problem that (maybe) caused the crash?

Well, that's not the problem. I wrote "delay: 3", no.
I can send you the graphics and the graphicsinfo.conf.
(the whole? Or the part of the exit door only?)

I'll check my graphicsinfo.conf one's more
very carefully.

Oh, I've one more problem with graphics:
If I want to change the graphic of the black orb bomb
it doesn't work:
In the game any graphic appears, but it's very strange:
It's always(!) a graphic from the
"classic graphics" directory, well, and always from the same
pcx.
Very nasty!
Maybe that's a bug!?

[Holger]

> I can send you the graphics and the graphicsinfo.conf.
> (the whole? Or the part of the exit door only?)

If in doubt, just send everything.

Have you checked the file "stderr.txt"? What does it say in its last lines after a crash (or "crash")?

[black orb graphics]
> Maybe that's a bug!?

Sometimes typos are hard to find... Have you found any corresponding error message about it in "stdout.txt" or "stderr.txt"?

[Daniel H.]

Sascha, you really need to post stderr.txt here or send it to Holger.
It would be nice if you were to post graphicsinfo.conf as well, but that is not as important.

Sascha, could you please check if this was the problem in your case, or if there is another problem that (maybe) caused the crash?

Well, that's not the problem. I wrote "delay: 3", no.
I can send you the graphics and the graphicsinfo.conf.
(the whole? Or the part of the exit door only?)

Did you have more than 0 frames? Anyway, please post (or somehow send) us stderr.txt.

If I want to change the graphic of the black orb bomb
it doesn't work:
In the game any graphic appears, but it's very strange:
It's always(!) a graphic from the
"classic graphics" directory, well, and always from the same
pcx.
Very nasty!
Maybe that's a bug!?

Not likely, other people have managed to change the graphics of black orb bombs in the past.

I am guessing that most likely, the problem is in the image file name. If you fail to give the exact file name for the exact element, then it willl use the default classic_graphics pcx file that contains black orb bombs.

Please check for these errors:

Code: Select all

CORRECT:
black_orb:                              RocksElements.pcx

SOME POSSIBLE ERRORS:
(There is one error with each of the following lines:)
black_ord:                              RocksElements.pcx
black_orb:                              RockElements.pcx
blackorb:                               RocksElements.pcx
black_orb:                              RocksElements.pxx

Also check to be sure that RocksElements.pcx (for example) really exists.

BTW - Is this in stable 3.1.2 or 3.2.0-8? Is this in Unix or Windows?
If it's in Unix, then the file names may be case sensitive.

[Sascha]

Is this in stable 3.1.2 or 3.2.0-8? Is this in Unix or Windows?
If it's in Unix, then the file names may be case sensitive.

I use 3.1.2 UNIX version.

I'll send the stderr.txt as soon as I can, but
at the moment I'm busy.

I'll send it to Holgers E-Mail.

[Sascha]

There is no stderr.txt or stdout.txt! no no no!
nothing!

[Daniel H.]

Right after you get out of playing Rocks 'n' Diamonds, a stderr.txt ALWAYS appears in the R&D Program Root Directory.

Are you sure that you are looking in the R&D Program Root Directory?

[Zomis]

Right after you get out of playing Rocks 'n' Diamonds, a stderr.txt ALWAYS appears in the R&D Program Root Directory.

Are you sure that you are looking in the R&D Program Root Directory?

AFAIK, not in the Unix versions.
Sascha, do you see anything in the console window after closing RND? If you do, copy all of it (from where you wrote "rocksndiamonds" to start the game and forward) and post it here. I think that's how Unix handles the stdout and stderr.

[Daniel H.]

Oops, sorry. I had forgotten the UNIX existed