Ubuntu
nemiver package

nemiver crashed with SIGSEGV in nemiver::IDebugger::Variable::build_qname()

Bug #327128 reported by Martin Olsson
6
Affects Status Importance Assigned to Milestone
nemiver
Fix Released
Critical
nemiver (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: nemiver

crashed the second time when I selected "dereference variable" from the right-click meny in the variables tab.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nemiver
Package: nemiver 0.6.4-1ubuntu1
ProcCmdline: nemiver valac -C test1.vala test2.vala
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: nemiver
StacktraceTop:
 nemiver::IDebugger::Variable::build_qname ()
 nemiver::IDebugger::Variable::build_qname ()
 nemiver::IDebugger::Variable::build_qname ()
 nemiver::VarListWalker::do_walk_variable ()
 nemiver::LocalVarsInspector::Priv::on_variable_dereferenced_signal ()
Title: nemiver crashed with SIGSEGV in nemiver::IDebugger::Variable::build_qname()
Uname: Linux 2.6.28-6-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Martin Olsson (mnemo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:nemiver::IDebugger::Variable::build_qname (
nemiver::IDebugger::Variable::build_qname (
nemiver::VarListWalker::do_walk_variable (
nemiver::LocalVarsInspector::Priv::on_variable_dereferenced_signal (this=<value optimized out>, a_var=<value optimized out>,
sigc::internal::slot_call2<sigc::bound_mem_functor2<void, nemiver::LocalVarsInspector::Priv, nemiver::common::SafePtr<nemiver::IDebugger::Variable, nemiver::common::ObjectRef, nemiver::common::ObjectUnref>, nemiver::common::UString const&>, void, nemiver::common::SafePtr<nemiver::IDebugger::Variable, nemiver::common::ObjectRef, nemiver::common::ObjectUnref> const, nemiver::common::UString const&>::call_it (rep=0x294ffc0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in nemiver:
importance: Undecided → Medium
Revision history for this message
Martin Olsson (mnemo) wrote :

FWIW, I was debugging valac 0.5.6 and the valac bug involved a stack overflow (I saw like more than 30K stack frames in gdb).

The test1.vala and test2.vala files contained the "class+enum" and "abstract class+class" posted by this guy:
http://mail.gnome.org/archives/vala-list/2009-February/msg00030.html

And the variables I was trying to deref was like "file" and "file->priv" inside vala_code_context_find_cycle_head().

Bug Watch Updater (bug-watch-updater)
Changed in nemiver:
status: Unknown → Fix Released
Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Martin,

Did you experienced this bug with latest nemiver, 0.6.5 was uploaded few days ago.
Thank for your feedback.

Daniel Holbach (dholbach)
Changed in nemiver (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Olsson (mnemo) wrote :

works

Changed in nemiver:
status: Incomplete → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in nemiver:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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