zapping crashed with SIGSEGV in strlen()

Bug #263045 reported by hvdm
30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zapping (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: zapping

Description: Ubuntu intrepid (development branch)
Release: 8.10

zapping:
  Installed: 0.10~cvs6-2
  Candidate: 0.10~cvs6-2
  Version table:
 *** 0.10~cvs6-2 0
        500 http://nl.archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/zapping
Package: zapping 0.10~cvs6-2
ProcAttrCurrent: unconfined
ProcCmdline: zapping
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: zapping
StacktraceTop:
 strlen () from /lib/libc.so.6
 g_strdup () from /usr/lib/libglib-2.0.so.0
 _cmd_register ()
 startup_cmd ()
 ?? ()
Title: zapping crashed with SIGSEGV in strlen()
Uname: Linux 2.6.27-2-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Tags: apport-crash
Revision history for this message
hvdm (henk-vandermolen) wrote :
Revision history for this message
Marcus Asshauer (mcas) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in zapping:
status: New → Incomplete
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:strlen () from /lib/libc.so.6
IA__g_strdup (str=0x5b8 <Address 0x5b8 out of bounds>)
_cmd_register (name=0x505cb4 "switch_mode", cfunc=0x43097e <py_switch_mode>,
startup_cmd () at /build/buildd/zapping-0.10~cvs6/src/cmd.c:371
startup_zapping (load_plugins=1, info=0x2334fd0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in zapping:
importance: Undecided → Medium
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in zapping:
status: Incomplete → Invalid
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.