apparmor_parser crashed with SIGSEGV in __libc_start_main()

Bug #675281 reported by Daniel J Blueman on 2010-11-14
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: apparmor

When booting the kernel 'apparmor=0', we see apparmor_parser crash multiple times on boot, which seems an avoidable oversight.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: apparmor 2.5.1~rc1-0ubuntu2
ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature'
Uname: Linux 2.6.37-020637rc1-generic x86_64
ApparmorStatusOutput:
 Error: command /usr/sbin/apparmor_status failed with exit code 4: You do not have enough privilege to read the profile set.
 apparmor module is loaded.
Architecture: amd64
Date: Sun Nov 14 19:50:25 2010
ExecutablePath: /sbin/apparmor_parser
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: BOOT_IMAGE=/vmlinuz-2.6.37-020637rc1-generic root=/dev/sda2 ro debug
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x40a14e: repnz scas %es:(%rdi),%al
 PC (0x0040a14e) ok
 source "%es:(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apparmor
StacktraceTop:
 ?? ()
 __libc_start_main (main=<value optimised out>, argc=<value optimised out>, ubp_av=<value optimised out>, init=<value optimised out>, fini=<value optimised out>, rtld_fini=<value optimised out>, stack_end=0x7fffa9878338) at libc-start.c:226
 ?? ()
 ?? ()
 ?? ()
Title: apparmor_parser crashed with SIGSEGV in __libc_start_main()
UserGroups:

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #626984, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers