Does not run when compiled for SDL on 64-bit Linux

[GoogleCodeExporter]

What steps will reproduce the problem?
   1. Compile using the SDL makefile on Linux
   2. Try running the resulting executable

What is the expected output?

   The program should run.

What do you see instead?

   The program terminates after a second or two without any console output or any visible indication that it has run (other than a short pause between hitting enter and receiving a shell prompt).

What version of the product are you using? On what operating system?

   Sangband 1.0.2 on 64-bit Ubuntu 10.04

Please provide any additional information below.

   If compiled to use the console, the program runs properly.

   If compiled for SDL and run under gdb, the program runs without problems (but is slow). gdb gives the following output (If the user exits the program immediately upon reaching the main menu):

Starting program: /home/jon/Sangband/sangband 
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffede12700 (LWP 16008)]
[Thread 0x7fffede12700 (LWP 16008) exited]
[New Thread 0x7fffede12700 (LWP 16009)]
[New Thread 0x7fffed611700 (LWP 16010)]
[Thread 0x7fffed611700 (LWP 16010) exited]
[Thread 0x7fffede12700 (LWP 16009) exited]

Program exited normally.

Original issue reported on code.google.com by jon.br...@gmail.com on 31 May 2011 at 12:11

[GoogleCodeExporter]

I just tested this following the directions here and didn't have a problem.
http://angband.oook.cz/forum/showpost.php?s=ae0b5182563d62c026bade70d7a8529f&p=4
1195&postcount=6

This was using ubuntu 10.10 64 bit version.

Original comment by jmidd...@gmail.com on 24 Jun 2011 at 3:01

[GoogleCodeExporter]

Did some further testing, found out that the result of:

sangband; echo $?

is zero, so it technically is "running" and even exiting successfully, just 
prematurely.

Then I found out that an SDL compile *will* in fact launch, but only if 
executed from a graphical application such as a file browser or the GNOME run 
dialog (Alt-F2). It will not launch from the command line unless started in gdb 
(in a graphical environment of course. I obviously don't expect it to run from 
the console without an X session, but most X applications will launch properly 
if executed, for instance, from xterm, gnome-terminal, or a shell script 
executed in a graphical environment. SDL Sangband will exit before displaying 
anything in all three cases). An interesting test case is with GNOME Commander, 
where it will launch if clicked on in one of the graphical panes, but will fail 
if launched from the command line at the bottom of the window.

I had at first been trying to execute Sangband from a gnome-terminal instance 
since I had compiled it there.

In summary:

Sangband will run normally (the things not marked with "presumably" are the 
ones I have actually tried):

When run from the command line in gdb.
When launched from nautilus.
When launched from one of the graphical panes in GNOME Commander.
When launched from the GNOME run dialog (including with "Run in terminal" 
checked).
Presumably when launched from any other graphical file browser, launcher, etc.

Sangband will exit prematurely:
When run from zsh (and presumably any other shell) in xterm.
When run from zsh, bash, dash, csh, ksh, or fish (and presumably any other 
shell) in gnome-terminal.
When run from a shell script launched from nautilus.
When run from the command line in GNOME Commander.
Presumably when run by any other means involving a command line or text-mode 
shell, except for the GNOME run dialog with "Run in terminal" checked.

Original comment by jon.br...@gmail.com on 10 Jul 2011 at 6:21