hmmm... BulletCandyV2 for linux (Ubuntu 8.04) you gave me gives a lovely singnal 11 in appstub when loading the levels.
If i remember that's a invalid memory segment access.
I checked out the Beta version which runs fine.
The path stuff is quite interesting.
I know that /proc is a virtual file directory containing all running process on the machine and have been trying to figure out how it works.
The man page may give clues http://linux.die.net/man/5/proc
though I did read somewhere that /proc may become redundant in the future.
After reading the article at LinuxQuestion.org. I think I have the answer
If i remember that's a invalid memory segment access.
I checked out the Beta version which runs fine.
The path stuff is quite interesting.
I know that /proc is a virtual file directory containing all running process on the machine and have been trying to figure out how it works.
The man page may give clues http://linux.die.net/man/5/proc
though I did read somewhere that /proc may become redundant in the future.
After reading the article at LinuxQuestion.org. I think I have the answer
/proc/self is a symbolic link to the process-ID subdir of /proc, e.g.
/proc/4323 when the pid of the process of this program is 4323.
Inside /proc/<pid> there is a symbolic link to the executable that is
running as this <pid>. This symbolic link is called "exe". So if we
read the path where the symlink /proc/self/exe points to we have the
full path of the executable.
/proc/4323 when the pid of the process of this program is 4323.
Inside /proc/<pid> there is a symbolic link to the executable that is
running as this <pid>. This symbolic link is called "exe". So if we
read the path where the symlink /proc/self/exe points to we have the
full path of the executable.