doodle crashed with SIGSEGV

Bug #1283259 reported by rajuramvani
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
doodle (Ubuntu)
New
Undecided
Unassigned

Bug Description

please resolve this problem.thanks.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: doodle 0.7.0-8
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic i686
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CrashCounter: 1
Date: Sat Feb 22 03:16:10 2014
ExecutablePath: /usr/bin/doodle
ProcCmdline: /usr/bin/doodle -d /var/lib/doodle/doodle.db -L /var/log/doodle.log -b /home
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 SHELL=/bin/sh
SegvAnalysis: Skipped: missing required field "Registers"
Signal: 11
SourcePackage: doodle
Stacktrace: No symbol table is loaded. Use the "file" command.
StacktraceTop:

Title: doodle crashed with SIGSEGV
UpgradeStatus: Upgraded to trusty on 2014-02-16 (5 days ago)
UserGroups:

Revision history for this message
rajuramvani (rajuramvani-gmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb72130a8 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xb6fd9bd0
StacktraceSource: #0 0xb72130a8 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:
 .
 Thread 4 (LWP 10904):
 #0 0xb77cb424 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xb5bff118

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Marc Deslauriers (mdeslaur) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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