Bug 684965

Summary: [abrt] gpsdrive-2.11-1.fc14: lat2radius: Process /usr/bin/gpsdrive was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Roman Melihhov <roman>
Component: gpsdriveAssignee: Kevin Fenzi <kevin>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: hicham.haouari, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:a2746570426cfe198afd7dcbef8a9902f2da46ae
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-14 22:19:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Roman Melihhov 2011-03-14 21:13:05 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 21912 bytes
cmdline: gpsdrive
component: gpsdrive
Attached file: coredump, 76472320 bytes
crash_function: lat2radius
executable: /usr/bin/gpsdrive
kernel: 2.6.35.11-83.fc14.x86_64
package: gpsdrive-2.11-1.fc14
rating: 4
reason: Process /usr/bin/gpsdrive was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300136515
uid: 500

How to reproduce
-----
1. connected SB-369 bluetooth GPS device
2. created link /dev/rfcomm0 to my device 00:01:53:02:DF:A5
3. started sudo gpsd /dev/rfcomm0
now when running gpsdrive it crashes
Comment 1 Roman Melihhov 2011-03-14 21:13:08 UTC 
Created attachment 484306 [details]
File: backtrace
Comment 2 Roman Melihhov 2011-03-14 22:19:31 UTC 
I'd restarted SB-369 and gpsd and everything is working, eventually...