Ubuntu
firefox package

firefox-bin crashed with SIGSEGV in toupper_w()

Bug #164789 reported by Wolf Canis on 2007-11-24

6

Affects		Status	Importance	Assigned to	Milestone
	firefox (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: firefox

Hello,
I did nothing special, I only called the page www.bbcnews.com and there the video

http://www.bbc.co.uk/mediaselector/check/player/nol/newsid_7100000/newsid_7108600?redirect=7108638.stm&news=1&bbwm=1&bbram=1&nbwm=1&nbram=1&asb=1

and firefox crashed. That's all. Version info etc. are in the crash report. If you are something missing or need more information, simply ask.

W. Canis

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Nov 24 04:50:10 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/firefox/firefox-bin
NonfreeKernelModules: fglrx ath_hal
Package: firefox 2.0.0.8+2nobinonly-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/firefox/firefox-bin
ProcCwd: /home/rh
ProcEnviron:
PATH=/home/rh/bin:/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: firefox
StacktraceTop:
toupper_w () from /usr/lib/libsmbclient.so.0
toupper_ascii () from /usr/lib/libsmbclient.so.0
strupper_m () from /usr/lib/libsmbclient.so.0
set_global_myname () from /usr/lib/libsmbclient.so.0
lp_load () from /usr/lib/libsmbclient.so.0
Title: firefox-bin crashed with SIGSEGV in toupper_w()
Uname: Linux rh-laptop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags:

Revision history for this message

Wolf Canis (wolf-canis) wrote on 2007-11-24:

#1

Dependencies.txt Edit (2.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (647 bytes, text/plain; charset="utf-8")
ExtensionSummary.txt Edit (1.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (48.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (669 bytes, text/plain; charset="utf-8")
Registers.txt Edit (474 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (959 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (15.5 KiB, text/plain; charset="utf-8")
pluginreg.dat.txt Edit (4.4 KiB, text/plain; charset="utf-8")
profiles.ini.txt Edit (169 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2007-11-27: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (201 bytes, text/plain)

StacktraceTop:__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libpthread.so.0
?? ()
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2007-11-27: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (14.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2007-11-27: Stack trace with source code

#4

StacktraceSource.txt Edit (202 bytes, text/plain)

Revision history for this message

Wolf Canis (wolf-canis) wrote on 2007-11-27: Re: [Bug 164789] Re: firefox-bin crashed with SIGSEGV in toupper_w()

#5

Hello,
how can I produce a i386 trace?
Or do I misunderstanding this mail?

W. Canis

Apport retracing service wrote:
> StacktraceTop:__kernel_vsyscall ()
> raise () from /lib/tls/i686/cmov/libpthread.so.0
> ?? ()
> ?? ()
> ?? ()
>
> ** Tags removed: need-i386-retrace
>
> ** Attachment added: "Stacktrace.txt (retraced)"
> http://launchpadlibrarian.net/10586937/Stacktrace.txt
>
>

Revision history for this message

Alexander Sack (asac) wrote on 2007-12-04:

#6

your crash report didn't yield the required information needed to evaluate this crash. Please submit new crash reports you get in future.

Thanks,
- Alexander

Changed in firefox:
status:	New → Invalid

Revision history for this message

Wolf Canis (wolf-canis) wrote on 2007-12-04:

#7

_usr_lib_firefox_firefox-bin.1000.crash Edit (25.5 MiB, text/html)

Hello,
here a new crash report.

Revision history for this message

Alexander Sack (asac) wrote on 2007-12-29:

#8

Hi,

please submit the crash report by (double) clicking on it (e.g. using gnome file manager). Otherwise, we won't be able to process it efficiently. The .crash files can be found in the /var/crash directory.

Thanks,
- Alexander

Revision history for this message

Wolf Canis (wolf-canis) wrote on 2007-12-30:

#9

Hello Alexander,
I haven't yet a Ubuntu box with Ubuntu-Java or Ubuntu-Flash at my disposal, I'm afraid. But you can simply click on the link in my initial report and you should get the crash.

Thanks in advance.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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