[Bug 161152] Re: nvclock crashed with SIGSEGV in __libc_start_main()

[Kees Cook]

** Description changed:

  Binary package hint: nvclock
  
  I noticed that adding 'nvclock -m 620 -n 300' to /etc/rc.local causes it
  to crash, and so does running it from the command line.
  
  It seems like nvclock communicates with the X server or nvidia module.
  After X is running, nvclock works as expected.
  
  ProblemType: Crash
  Architecture: amd64
  Date: Mon Nov  5 15:33:08 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/nvclock
  NonfreeKernelModules: vmnet vmblock vmmon nvidia
  Package: nvclock 0.8b2-1ubuntu1
  PackageArchitecture: amd64
  ProcCmdline: nvclock -m 620 -n 300
  ProcCwd: /
  ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin
  Signal: 11
  SourcePackage: nvclock
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main () from /lib/libc.so.6
   ?? ()
  Title: nvclock crashed with SIGSEGV in __libc_start_main()
  Uname: Linux veyron 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
  UserGroups: system users
+ SegvAnalysis:
+  Segfault happened at: 0x406423 <mkdir at plt+19739>:	repnz scas %es:(%rdi),%al
+  PC (0x00406423) ok
+  source "%es:(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
+  destination "%al" ok
+ SegvReason: reading NULL VMA

-- 
nvclock crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/161152
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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