Bug#564937: Attaching info with libsm6-dbg
Hi,
that problem with backtrace was perhaps my misread/misunderstand of the backtrace.
No matter, it seems that this problem has been solved in original, because I haven't reproduced it during about 4-5 hours of gameplay
So, you can close this bug...
Thanks
Jakub Lucký
2010/6/5 Julien Cristau
<jcristau@debian.org>
severity 564937 normal
tag 564937 moreinfo
kthxbye
On Fri, Apr 2, 2010 at 23:41:29 +0200, Jakub Lucký wrote:
> Hi
>
> I installed libsm6-dbg and performed gdb run
>
> see attached
>
> Jakub
[...]
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xec831b70 (LWP 31674)]
> 0xebd160b0 in ?? ()
> (gdb) backtrace full
> #0 0xebd160b0 in ?? ()
> No symbol table info available.
> #1 0xf7a2b04c in snd_pcm_recover () from /usr/lib/libasound.so.2
> No symbol table info available.
> #2 0xf7f4dd2a in ?? () from /usr/lib/libSDL-1.2.so.0
> No symbol table info available.
> #3 0xf7f1fa72 in ?? () from /usr/lib/libSDL-1.2.so.0
> No symbol table info available.
> #4 0xf7f2787e in ?? () from /usr/lib/libSDL-1.2.so.0
> No symbol table info available.
> #5 0xf7f7402d in ?? () from /usr/lib/libSDL-1.2.so.0
> No symbol table info available.
> #6 0xf7e45585 in start_thread () from /lib/i686/cmov/libpthread.so.0
> No symbol table info available.
> #7 0xf7b7929e in clone () from /lib/i686/cmov/libc.so.6
> No symbol table info available.
This is a completely different error from the first one in this thread
(sigsegv in libasound instead of sigill in libSM). This one doesn't
seem to be related to libSM at all.
Can you still reproduce the bug, and if so can you please clarify which
issue it is?
Cheers,
Julien
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMCli3AAoJEDEBgAUJBeQMapsP/3DO07Nmh349HlHhqj5/5+Gv
jqwYHjSqZp00uhEIXhhsw0jIumHHmnVed5XZ2c+N9huseIlwLK0UIwgNVE8eW009
16/aPsRBF6L2nCaYR9+SBJmQQQbFfQ4CarCQABHWMAex+lZ641sePQqDwcAViUKC
auQAaHXe0fD9IUuyq7jd4oJlfWpB0OYByMp0ls+NHNcm4AIA3Bm47DJE22fzGZ5q
Js7xe5jnqjkS94ychVheASyGAitbodJ6IXvWT4wr0RyM61xFacAUC61/IyNP3kam
PZ9agrecqC/dQzil1goAPUkv1US9I+X1Xv6w5xdYOoFWsSGWImhsxJq8JPdYPT/A
Y0kjUKDD77Jhk3P7yuaZ0qcuxh+U/lnC58Ug0WOEb3TQ+Qu0lkiv1iqVjZyvVpAn
S12LMTo11YRFxTcL5F2qU1s7ICTyqENDHXvJJqGY4P+W2x7Nwpe9GiPR6uAZYxpF
91Rr53GcRN8ARB5f1WcnU6pch+RwShBZ1S/ARyBQ5J/4n0H+u4gvKgkiyVQ7QO92
Q95vhX6zBA+bVhfoNjQ2JPvtSsVTTPgddBWXCa/xLQOUtWaD279qmai6gcWk5F7s
M/a86FlkcCF4Z4m91jQzwy38xsECxLXdYULUdwnL46imglrDRLu59TnnhSl2B0Tj
qDHDhSA1EBLJeuxZu+us
=fPsz
-----END PGP SIGNATURE-----
Reply to: