Ubuntu
mir package

kate crashed with SIGSEGV in make_protobuf_object() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()

Bug #1675749 reported by dinamic on 2017-03-24

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Mir	New	High	Unassigned
	kate (Ubuntu)	New	High	Unassigned
	mir (Ubuntu)	New	High	Unassigned

Bug Description

kate crashed with SIGSEGV

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: kate 4:16.12.3-0ubuntu1 [modified: usr/share/applications/org.kde.kate.desktop]
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity8
Date: Fri Mar 24 13:34:53 2017
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/kate
InstallationDate: Installed on 2016-12-12 (101 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
ProcCmdline: kate -b
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kate
StacktraceTop:
()
() at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
() at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
() at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
() at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
Title: kate crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

Tags:

Revision history for this message

dinamic (dinamic6661) wrote on 2017-03-24:

#1

Dependencies.txt Edit (12.6 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (92.4 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (290 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (111.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (787 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (8.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2017-03-24:

#2

StacktraceTop:
?? ()
make_protobuf_object () at ./src/client/rpc/../make_protobuf_object.h:29
mir::client::rpc::MirProtobufRpcChannel::on_data_available() (this=0x55bace40b1d0) at ./src/client/rpc/mir_protobuf_rpc_channel.cpp:457
operator() () at ./src/client/rpc/stream_socket_transport.cpp:40
_ZNSt17_Function_handlerIFvRKSt10shared_ptrIN3mir6client3rpc15StreamTransport8ObserverEEEZNS3_18TransportObservers17on_data_availableEvEUlT_E_E9_M_invokeERKSt9_Any_dataS8_.lto_priv.368 (__functor=..., __args#0=...) at /usr/include/c++/6/functional:1731

Revision history for this message

Apport retracing service (apport) wrote on 2017-03-24: Stacktrace.txt

#3

Stacktrace.txt Edit (5.2 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-03-24: StacktraceSource.txt

#4

StacktraceSource.txt Edit (4.1 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2017-03-24: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (16.5 KiB, text/plain)

Changed in kate (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Daniel van Vugt (vanvugt) on 2017-04-05

information type:	Private → Public
summary:	- kate crashed with SIGSEGV + kate crashed with SIGSEGV in make_protobuf_object() from + mir::client::rpc::MirProtobufRpcChannel::on_data_available()
Changed in mir:
importance:	Undecided → High
Changed in kate (Ubuntu):
importance:	Medium → High
Changed in mir (Ubuntu):
importance:	Undecided → High

Revision history for this message

Alan Griffiths (alan-griffiths) wrote on 2017-08-21:

#6

Probably the same cause as lp:1666181 (but not marking as dup yet as need to confirm the problem isn't gtk-mir/qtubuntu)

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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