obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()

Bug #1568656 reported by prakash poudel
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libopenobex (Ubuntu)
New
Undecided
Unassigned

Bug Description

-

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: libopenobex2 1.7.1-5
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Apr 10 18:41:17 2016
Dependencies:
 gcc-6-base 6-20160405-0ubuntu1
 libc6 2.23-0ubuntu2
 libgcc1 1:6-20160405-0ubuntu1
 libudev1 229-4ubuntu1
 libusb-1.0-0 2:1.0.20-1
ExecutablePath: /usr/sbin/obex-check-device
InstallationDate: Installed on 2016-03-16 (25 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/sbin/obex-check-device 0bda
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f4224bef994 <__GI_____strtoul_l_internal+68>: movsbq (%r14),%rax
 PC (0x7f4224bef994) ok
 source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libopenobex
StacktraceTop:
 __GI_____strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=<optimized out>, loc=0x7f4224f79420 <_nl_global_locale>) at ../stdlib/strtol_l.c:293
 main ()
Title: obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()
UpgradeStatus: Upgraded to xenial on 2016-03-29 (12 days ago)
UserGroups:

Revision history for this message
prakash poudel (poudelprakash20) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1553358, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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