dnscrypt-proxy crashed with SIGSEGV

Bug #1703186 reported by james truax
98
This bug affects 10 people
Affects Status Importance Assigned to Milestone
dnscrypt-proxy (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

i dont know

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: dnscrypt-proxy 1.9.5-1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
Date: Sun Jul 9 03:01:11 2017
ExecutablePath: /usr/sbin/dnscrypt-proxy
InstallationDate: Installed on 2017-07-07 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/sbin/dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
Signal: 11
SourcePackage: dnscrypt-proxy
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: dnscrypt-proxy crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
james truax (procon2) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 request_find_from_trans_id (trans_id=23217, base=0x557bcd182560) at evdns.c:492
 reply_parse (base=0x557bcd182560, packet=0x557bcd183cc2 "Z\261\201\200", length=44, isudp=isudp@entry=0) at evdns.c:1148
 evdns_request_read_cb_tcp (bev=0x557bcd183950, ctx=0x557bcd1837f0) at evdns.c:906
 bufferevent_readcb (fd=10, event=<optimized out>, arg=0x557bcd183950) at bufferevent_sock.c:186
 event_process_active_single_queue (activeq=0x557bcd1622b0, base=0x557bcd182e60) at event.c:1368

Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Changed in dnscrypt-proxy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in dnscrypt-proxy (Ubuntu):
status: New → Confirmed
information type: Private → 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.