brasero crashed with SIGSEGV in dl_iterate_phdr()

[Spencer Crawford]

Binary package hint: brasero

Crashes, also when used with Rhythm Box to burn cd, app launches, select tracks to burn, app gives error, ejects disc. Tried various media, same issue.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: brasero 2.31.92-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Mon Sep 20 17:24:21 2010
ExecutablePath: /usr/bin/brasero
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcCmdline: brasero
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x302d6b1: mov (%eax),%esi
 PC (0x0302d6b1) ok
 source "(%eax)" (0x00000034) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /lib/libc.so.6
 dl_iterate_phdr () from /lib/libc.so.6
 _Unwind_Find_FDE () from /lib/libc.so.6
 ?? () from /lib/libgcc_s.so.1
 ?? () from /lib/libgcc_s.so.1
Title: brasero crashed with SIGSEGV in dl_iterate_phdr()
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 _Unwind_IteratePhdrCallback (info=0xb6555de8, size=40, ptr=0xb6555e2c)
 *__GI___dl_iterate_phdr (
 _Unwind_Find_FDE (pc=0xc1c85d, bases=0xb6556038)
 ?? () from /lib/libgcc_s.so.1
 ?? () from /lib/libgcc_s.so.1

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

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!.