qtcreator crashed with SIGSEGV

[Robie Basak]

I installed ubuntu-sdk in a fresh i386 VM (I tried amd64 first, but that doesn't seem to have an installable ubuntu-emulator). I set up a normal user and ran "ubuntu-sdk" as that user. I followed the wizard, setting up a 15.10 framework i386 thing (kit?) and asked for it to take me to the Devices page so I could add an emulator. It crashes every time. I cannot seem to get to the main window without it crashing.

Differences from a regular desktop:

No ubuntu-desktop installed - just an i386 cloud image with ubuntu-sdk (and recommends) installed.

I hacked debootstrap by diverting and wrapping it to set http_proxy. This seems to work without issues.

I'm using "ssh -X" to get the GUI onto my real desktop machine. Maybe not having accelerated X is the biggest different from a regular desktop causing this crash?

That's it.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: qtcreator 3.1.1-0ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
Uname: Linux 3.19.0-13-generic i686
ApportVersion: 2.17-0ubuntu2
Architecture: i386
Date: Sat Apr 11 17:52:17 2015
Disassembly: => 0xb3d777d3: Cannot access memory at address 0xb3d777d3
ExecutablePath: /usr/bin/qtcreator
JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found.
ProcCmdline: hostname
SegvAnalysis:
 Segfault happened at: 0xb3d777d3: Cannot access memory at address 0xb3d777d3
 PC (0xb3d777d3) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: qtcreator
Stacktrace:
 #0 0xb3d777d3 in ?? ()
 No symbol table info available.
 #1 0x09d44660 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
Title: qtcreator crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: autopilot sudo

[Robie Basak (racb)]

No private information here as it was from a freshly installed VM.

[Apport retracing service (apport)]

Stacktrace:
 #0 0xb3d777d3 in ?? ()
 No symbol table info available.
 #1 0x09d44660 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceSource:
 #0 0xb3d777d3 in ?? ()
 #1 0x09d44660 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for qtcreator-plugin-valgrind
no debug symbol package found for qtcreator-plugin-qnx
no debug symbol package found for qtcreator-plugin-remotelinux
no debug symbol package found for qtcreator-plugin-cmake
no debug symbol package found for libflac8

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Robie Basak (racb)]

No idea about missing debug symbols, but this happened on a fresh Vivid VM with current packages.