[Bug 199821] Re: balazar crashed with SIGSEGV in pthread_mutex_lock()

[Kees Cook]

** Description changed:

  Binary package hint: balazar
  
  whenever i start up my computer it says "Error program balazer cannot
  start program terminated" when i try to start it up again it re-boots my
  computer for no reason.....i need this bug to be fixed because i just
  got this computer and if im having problems with it i wont be able to
  use it then....if this  bug keeps showing up then i wont be able to use
  Linux again.....i REALLY need this bug fixed..oh...and the last time i
  opened it up again i got a virus.....i had to reinstall Linux.....this
  is a problem
  
  ProblemType: Crash
  Architecture: i386
  Date: Sat Mar  8 09:06:23 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/games/balazar
  InterpreterPath: /usr/bin/python2.5
  NonfreeKernelModules: ath_hal
  Package: balazar 0.3.4.ds1-2ubuntu1
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python -O /usr/games/balazar
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: balazar
  Stacktrace:
   #0  0xb7f49540 in pthread_mutex_lock ()
      from /lib/tls/i686/cmov/libpthread.so.0
   #1  0xb77806eb in ?? () from /usr/lib/libopenal.so.0
   #2  0x00000000 in ?? ()
  StacktraceTop:
   pthread_mutex_lock ()
   ?? () from /usr/lib/libopenal.so.0
   ?? ()
  Title: balazar crashed with SIGSEGV in pthread_mutex_lock()
  Uname: Linux 2.6.24-11-generic i686
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video
+ SegvAnalysis:
+  Segfault happened at: 0xb7f49540 <pthread_mutex_lock+32>:	mov    0xc(%edi),%edx
+  PC (0xb7f49540) ok
+  source "0xc(%edi)" (0x0000000c) not located in a known VMA region (needed readable region)!
+  destination "%edx" ok
+ SegvReason: reading NULL VMA

-- 
balazar crashed with SIGSEGV in pthread_mutex_lock()
https://bugs.launchpad.net/bugs/199821
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs