merkaartor crashed with SIGSEGV in gps_sock_read()

Bug #1699655 reported by judith
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gpsd (Ubuntu)
Won't Fix
Undecided
Unassigned
merkaartor (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

bug gps

Error transferring http://www.openstreetmap.org/api/0.6/map?bbox=-180.000000,-87.976103,405.099370,89.092399 - server replied: Bad Request

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: merkaartor 0.18.3+ds-1build2
ProcVersionSignature: Ubuntu 4.11.0-8.13-generic 4.11.6
Uname: Linux 4.11.0-8-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Thu Jun 22 05:59:25 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/merkaartor
InstallationDate: Installed on 2016-12-25 (179 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: merkaartor
SegvAnalysis:
 Segfault happened at: 0x7fd61b412b29 <gps_sock_read+25>: cmpb $0xa,0x10(%r12)
 PC (0x7fd61b412b29) ok
 source "$0xa" ok
 destination "0x10(%r12)" (0x00000010) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: merkaartor
StacktraceTop:
 gps_sock_read () at /usr/lib/x86_64-linux-gnu/libgps.so.22
 gps_read () at /usr/lib/x86_64-linux-gnu/libgps.so.22
 gpsmm::read() () at /usr/lib/x86_64-linux-gnu/libgps.so.22
 ()
 ()
Title: merkaartor crashed with SIGSEGV in gps_sock_read()
UpgradeStatus: Upgraded to artful on 2017-06-19 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
judith (josselyn) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gps_sock_read () from /tmp/apport_sandbox_Dwqnyn/usr/lib/x86_64-linux-gnu/libgps.so.22
 gps_read () from /tmp/apport_sandbox_Dwqnyn/usr/lib/x86_64-linux-gnu/libgps.so.22
 gpsmm::read() () from /tmp/apport_sandbox_Dwqnyn/usr/lib/x86_64-linux-gnu/libgps.so.22
 QGPSDDevice::onDataAvailable (this=0x56036adc5c60) at GPS/qgpsdevice.cpp:1006
 QGPSDDevice::run (this=0x56036adc5c60) at GPS/qgpsdevice.cpp:992

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in merkaartor (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Tyler Hicks (tyhicks) wrote :

I believe that this crash is in libgps from gpsd.

Changed in merkaartor (Ubuntu):
status: New → Invalid
Revision history for this message
Tyler Hicks (tyhicks) wrote :

I'm making this bug public as it looks to be the same crash as what's in bug #903959 which is already public.

information type: Private Security → Public Security
information type: Public Security → Public
Revision history for this message
Miriam España Acebal (mirespace) wrote :

Hi,

While doing some bug cleanup, I found this old bug.

First of all, thank you for reporting this bug to Ubuntu.

Ubuntu 16.10 (yakkety) reached end-of-life on July 20 2017, so I'm afraid this bug can't be fixed. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner, but it appears to be no further action possible at this time.

Apart from that, the request to get the map in merkaartor to openstreetmap logged ( http://www.openstreetmap.org/api/0.6/map?bbox=-180.000000,-87.976103,405.099370,89.092399 ) leads to a bad request because 405.099370 > 180, being 180 a boundary when using geographics coordinates [1]. My guess is that this out-of-boundaries ended in a memory writing issue due to bad/impossible allocation of memory through merkaartor and later, gpsd.

Due to the above, I'm marking this bug as "Won't fix".

[1] https://spatialreference.org/ref/epsg/wgs-84/

Changed in gpsd (Ubuntu):
status: New → Won't Fix
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.