xneur crashed with SIGSEGV in realloc()

Bug #545836 reported by hypnose
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
X Neural Switcher
Confirmed
High
Unassigned

Bug Description

Binary package hint: xneur

Віключается gxneur

ProblemType: Crash
Architecture: i386
Date: Wed Mar 24 11:03:05 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/xneur
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100323)
Package: xneur 0.9.5.1-2
ProcCmdline: xneur
ProcEnviron:
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0xbcdef3 <realloc+67>: mov 0x4(%edx),%eax
 PC (0x00bcdef3) ok
 source "0x4(%edx)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xneur
StacktraceTop:
 realloc () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: xneur crashed with SIGSEGV in realloc()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
hypnose (sergej-korzhov) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 *__GI___libc_realloc (oldmem=0x18, bytes=1) at malloc.c:3769
 buffer_clear (p=0x82a91f8) at buffer.c:150
 buffer_save_and_clear (p=0x82a91f8, window=18874375)
 program_update (p=0x8227aa8) at program.c:290
 program_process_input (p=0x8227aa8) at program.c:390

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xneur (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
security vulnerability: yes → no
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xneur (Ubuntu):
status: New → Confirmed
Revision history for this message
Alexey Shil (ashl1future) wrote :

Is this bug reproducible on the latest 0.15.0 release?

affects: xneur (Ubuntu) → xneur
Changed in xneur:
importance: Medium → High
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.