lat_ctx crashed with SIGSEGV

[Amit Kucheria]

Binary package hint: lmbench

I was running lat_ctx on Gutsy with the following cmdline:
/usr/lib/lmbench/bin/i686-pc-linux-gnu/lat_ctx -N 2 2 4 8 16 32 64 128

ProblemType: Crash
Architecture: i386
Date: Thu Sep 27 13:09:16 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/lmbench/bin/i686-pc-linux-gnu/lat_ctx
NonfreeKernelModules: cdrom
Package: lmbench 3.0-a7-1
PackageArchitecture: i386
ProcCmdline: /usr/lib/lmbench/bin/i686-pc-linux-gnu/lat_ctx -W 100 2 4 8 16 32 64 128 -N 2
ProcCwd: /tmp
ProcEnviron:
 SHELL=/bin/bash
 PATH=/bin:/usr/bin:/home/amit/bin:/usr/local/bin:/usr/X11R6/bin:/sbin:/usr/sbin
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: lmbench
Stacktrace:
 #0 0x08048f22 in ?? ()
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 13714):
 #0 0x08048f22 in ?? ()
 #1 0x00000000 in ?? ()
Title: lat_ctx crashed with SIGSEGV
Uname: Linux gollum 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0x8048f22 <sched_setaffinity@plt+638>: mov 0x4(%eax),%eax
 PC (0x08048f22) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:create_daemons ()
initialize ()
benchmp_child ()
benchmp ()
main ()

[Boniek (boniek12p)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Boniek (boniek12p)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!