You need to bring out the big guns
):
> Debian Games Team
>
> If you wish to submit further information on this problem, please
> send it to 674...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 674597
gt; send it to 674...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 674597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674597
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
[Sebastian Reichel]
> Start goplay, select the first game (currently "0ad"). Next press the
> up key from the arrows keys [0] and it will segfault.
Thank you. With this description, I can reproduce it. The segfault
give this backtrace:
(gdb) bt
#0 __strlen_sse2 () at ../sysdeps/i386/i686/multi
Hi,
On Tue, Jan 15, 2013 at 10:32:57AM +0100, Petter Reinholdtsen wrote:
> > goplay segfauls, if you select the first entry and then change to the
> > previous (non existing) entry by using the arrow keys. backtrace is
> > not that helpful, because goplay has no debugging symbols available.
>
>
[Sebastian Reichel 2012-05-25]
> goplay segfauls, if you select the first entry and then change to the
> previous (non existing) entry by using the arrow keys. backtrace is
> not that helpful, because goplay has no debugging symbols available.
I tried to reproduce this, but suspect I did not rea
Package: goplay
Version: 0.5-1.1
Severity: normal
Hi,
goplay segfauls, if you select the first entry and then change
to the previous (non existing) entry by using the arrow keys.
backtrace is not that helpful, because goplay has no debugging
symbols available.
(gdb) bt
#0 __strlen_sse2 () at ..
8 matches
Mail list logo
