Bug 407843 – crash in Calculator: calculation 3725 dec<>bi...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 407843 - crash in Calculator: calculation 3725 dec<>bi...


Summary:	crash in Calculator: calculation 3725 dec<>bi...


Status:	RESOLVED DUPLICATE of bug 354730

Product:	gnome-calculator
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Rich Burridge
QA Contact:	Rich Burridge

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-14 12:50 UTC by stefankaerst
Modified:	2007-02-14 15:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description stefankaerst 2007-02-14 12:50:57 UTC

What were you doing when the application crashed?
calculation 3725 dec<>bin and I then tried to do 3725 mod 2 


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 32292864 vsize: 0 resident: 32292864 share: 0 rss: 12603392 rss_rlim: 0
CPU usage: start_time: 1171457022 rtime: 0 utime: 118 stime: 0 cutime:114 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gcalctool'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225185616 (LWP 12943)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 110660

Thread 1 (Thread -1225185616 (LWP 12943))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 __assert_fail
from /lib/tls/i686/cmov/libc.so.6
#8 matherr
#9 matherr
#10 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#18 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#25 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#35 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#37 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 matherr
#40 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#41 ??
#0 __kernel_vsyscall

Comment 1 Teppo Turtiainen 2007-02-14 15:18:23 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 354730 ***