Ubuntu
bamf package

bamfdaemon crashed with SIGABRT in ext_wmatch()

Bug #940992 reported by Alex. K. on 2012-02-25

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	bamf (Ubuntu)	New	Undecided	Unassigned

Bug Description

sometimes happens

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bamfdaemon 0.2.110-0ubuntu1
Uname: Linux 3.0.19-1-ac100 armv7l
ApportVersion: 1.93-0ubuntu2
Architecture: armhf
CrashCounter: 1
Date: Sat Feb 25 20:35:48 2012
ExecutablePath: /usr/lib/bamf/bamfdaemon
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
SHELL=/bin/bausername
PATH=(custom, no user)
LANG=ru_RU.UTF-8
Signal: 6
SourcePackage: bamf
StacktraceTop: ext_wmatch (opt=<error reading variable: Cannot access memory at address 0x134>, opt@entry=<error reading variable: Cannot access memory at address 0x170>, pattern=<error reading variable: Cannot access memory at address 0x140>, pattern@entry=<error reading variable: Cannot access memory at address 0x170>, string=0xb6abfd84 L"\x6975622f\x622f646c\x646c6975\x6c672f64\x2e326269\x2e322d30\x312e3133\x2f2e2f38\x2f6f6967\x75626467\x6e6f6373\x7463656e\x2e6e6f69c\x67616c66\x20262073\x47414c46\x494e495f\x4c414954\x44455a49", string@entry=<error reading variable: Cannot access memory at address 0x170>, string_end=<error reading variable: Cannot access memory at address 0x138>, string_end@entry=<error reading variable: Cannot access memory at address 0x170>, no_leading_period=<error reading variable: Cannot access memory at address 0x174>, no_leading_period@entry=<error reading variable: Cannot access memory at address 0x170>, flags=<error reading variable: Cannot access memory at address 0x178>, flags@entry=<error reading variable: Cannot access memory at address 0x170>, alloca_used=<optimized out>, alloca_used@entry=<error reading variable: Cannot access memory at address 0x170>) at fnmatch_loop.c:1112
Title: bamfdaemon crashed with SIGABRT in ext_wmatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Alex. K. (alex-kovtonuk) wrote on 2012-02-25:

CoreDump.gz Edit (726.4 KiB, application/x-gzip)
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (916 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (31.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (778 bytes, text/plain; charset="utf-8")
Registers.txt Edit (549 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.5 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-12-10: No launchpad retracing

Unsetting the need retracing tag. The crash report is too old to be processed by Apport, we did not have the ability to process crashes for the ARM platform until now.

tags:

removed: need-armhf-retrace

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntubamf package