Ubuntu
worker package

worker crashed with SIGSEGV in strchrnul()

Bug #913077 reported by Hans Joachim Desserud
74
This bug affects 13 people
Affects Status Importance Assigned to Milestone
worker (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Segfaulted when attempting to run worker

$ worker
Segmentation fault (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: worker 2.18.1-1
ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0
Uname: Linux 3.2.0-8-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sat Jan 7 11:51:02 2012
ExecutablePath: /usr/bin/worker
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: worker
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x9eeb97 <strchrnul+23>: mov (%eax),%cl
 PC (0x009eeb97) ok
 source "(%eax)" (0x00000006) not located in a known VMA region (needed readable region)!
 destination "%cl" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: worker
StacktraceTop:
 strchrnul () from /lib/i386-linux-gnu/libc.so.6
 vfprintf () from /lib/i386-linux-gnu/libc.so.6
 __vfprintf_chk () from /lib/i386-linux-gnu/libc.so.6
 __vsyslog_chk () from /lib/i386-linux-gnu/libc.so.6
 __syslog_chk () from /lib/i386-linux-gnu/libc.so.6
Title: worker crashed with SIGSEGV in strchrnul()
UpgradeStatus: Upgraded to precise on 2011-12-17 (20 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Hans Joachim Desserud (hjd) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 strchrnul () at ../sysdeps/i386/strchrnul.S:68
 __find_specmb (format=0x6 <Address 0x6 out of bounds>) at printf-parse.h:99
 _IO_vfprintf_internal (s=Cannot access memory at address 0x2525
 ___vfprintf_chk (fp=0x83cca78, flag=1, format=0x6 <Address 0x6 out of bounds>, ap=0xbfca890c "\313\215\312\277\004\222\024") at vfprintf_chk.c:35
 __GI___vsyslog_chk (pri=<optimized out>, flag=1, fmt=0x6 <Address 0x6 out of bounds>, ap=0xbfca890c "\313\215\312\277\004\222\024") at ../misc/syslog.c:224

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in worker (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Hans Joachim Desserud (hjd)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in worker (Ubuntu):
status: New → Confirmed
Revision history for this message
Lem (lem-jjr) wrote :

Happens on the AMD64 build as well..

Revision history for this message
rai4shu2 (rai4shu2) wrote :

Hello. I just installed Xubuntu beta 2 amd64 (and updated). I always build from source, so it was a little surprising to run into this myself (I'm using latest upstream AVFS and Worker). Anyway, after some advice, I recompiled AVFS with this additional option:

-D_FORTIFY_SOURCE=0

Add that in the "Makefile" for AVFS (in the line for CPPFLAGS). You might need it for Worker. I don't know, but Worker gets past the segfault once you do that.

Revision history for this message
Jean Goudreault (pulsarjg) wrote :

See also : bug # 994464 and bug # 995642

Revision history for this message
Tomas Pospisek (tpo-deb) wrote :

See also bug #1013607

Revision history for this message
rpkrawczyk (rpkrawczyk) wrote :

Before putting much effort into this bug: is this fixed in the new Ubuntu release (14.04)?

Revision history for this message
Lem (lem-jjr) wrote :

Yes, this has been fixed since 12.10 if I recall correctly. Definitely since 13.04 anyway. The bug was in avfs. https://bugs.launchpad.net/ubuntu/+source/avfs/+bug/1013607

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for the info Lem. I'm not able to reproduce this on Ubuntu 14.04 either, FWIW. I'm closing this as Fix Released then. :)

Regarding 12.04, I see that bug 1013607 has a task for potentially fixing that issue in Precise too. Would that be sufficient to solve this or would worker need an update too?

Also, bug 994464 looks like a duplicate of this bug, should it be marked as such?

Changed in worker (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Lem (lem-jjr) wrote :

Yes indeed Hans.. I wondered where I had commented about 12.10, and bug 994464 was it. I would say you're right as marking it a duplicate of this bug.

I think Worker would be fine if the avfs bug was fixed in Precise, seeing as bug 995642 mentions Worker working fine when compiled without avfs support.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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