On Fri, May 20, 2005 at 04:05:53PM +0200, Bartosz Fenski aka fEnIo wrote:
On Thu, May 19, 2005 at 04:13:55AM -0700, Steve Langasek wrote:
Here's the (not so useful) backtrace:
Since I don't have access to alpha desktop it would be quite hard to debug
the problem.
One more question. Does
On Thu, May 19, 2005 at 04:13:55AM -0700, Steve Langasek wrote:
Here's the (not so useful) backtrace:
[...]
Thanks Steve.
Since I don't have access to alpha desktop it would be quite hard to debug
the problem.
One more question. Does it segfault with `asc -q` switch?
regards
fEnIo
--
On Fri, May 20, 2005 at 04:05:53PM +0200, Bartosz Fenski aka fEnIo wrote:
Since I don't have access to alpha desktop it would be quite hard to debug
the problem.
I doubt this is relevant for the bug, but Valgrind shows several errors in
the memory handling. For instance, asc allocates memory
On Wed, May 18, 2005 at 08:29:38PM +0200, Falk Hueffner wrote:
Package: asc
Version: 1.16.0.0-1
Severity: grave
When I start asc, I get a screen with some aircrafts for a second or
so, and then:
[EMAIL PROTECTED]:~% asc
open /dev/sequencer: No such device
zsh: abort (core dumped) asc
Here's the (not so useful) backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x000120111a2c in putchar ()
(gdb) bt
#0 0x000120111a2c in putchar ()
#1 0x000120111dd0 in putchar ()
#2 0x0001200c5374 in putchar ()
#3 0x0001200c5228 in putchar ()
#4
Package: asc
Version: 1.16.0.0-1
Severity: grave
When I start asc, I get a screen with some aircrafts for a second or
so, and then:
[EMAIL PROTECTED]:~% asc
open /dev/sequencer: No such device
zsh: abort (core dumped) asc
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT
6 matches
Mail list logo
