No response from the original reporter, and the other reporter says it's
no longer occurring. So I'm assuming this was a driver problem.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sat, Dec 01, 2007 at 02:04:49AM -0500, Ari Pollak wrote:
Could you try to get a backtrace by running ulimit -c unlimited before
running gltron, and then opening the coredump in gdb?
I've no idea why, but it's working fine today :-/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
PS: ...oops, I see I wasn't the one who originally reported this bug.
Nevertheless I was seeing the same symptoms some time (a few weeks?)
ago, and can't reproduce the problem anymore. The only important
thing I can think of that's happened to my system since is the libc
upgrade to 2.7.
--
Could you try to get a backtrace by running ulimit -c unlimited before
running gltron, and then opening the coredump in gdb?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: gltron
Version: 0.70final-8
Severity: important
Selecting GAME in the startup screen works fine. Then, upon selecting
START GAME, gltron crashes. I can very briefly see that the window content
chages before the crash. Here is what gltron reports on the console:
~$ gltron
[status]
5 matches
Mail list logo