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 513395 - Evolution crashes when lauch the first time - critical warning
Evolution crashes when lauch the first time - critical warning
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 510557 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-31 10:05 UTC by Jeff Cai
Modified: 2013-09-13 00:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24

Attachments
check the parameter before calling camel_url_new (2.70 KB, patch)
2008-02-01 10:39 UTC, Jeff Cai 		committed Details | Review

Description Jeff Cai 2008-01-31 10:05:26 UTC 
Steps to reproduce:
1.Start Evolution
2.Evolution crashes
3. 


Stack trace:
Distribution:                 Solaris Express Developer Edition 1/08 snv_79b X86
Gnome Release: 2.21.5 2008-01-28 (Sun Microsystems, Inc.)
BugBuddy Version: 2.20.1

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus

Memory status: size: 158056448 vsize: 158056448 resident: 25657344 share: 0 rss: 25657344 rss_rlim: 0
CPU usage: start_time: 0 rtime: 149 utime: 1261374 stime: 236355 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

29543:	evolution
 d12f3f85 waitid   (0, 73b2, 8046160, 3)
 d12e3826 waitpid  (73b2, 80462c4, 0) + 70
 d10b139a g_spawn_sync (0, 83b67c0, 0, 4, 0, 0) + 346
 d10b174e g_spawn_command_line_sync (83b2510, 0, 0, 0, 804634c) + 5a
 cccb15cf __1cNrun_bug_buddy6Fpkclp0_b_ (8087500, 7367, 0) + 6b
 cccb1825 __1cMcheck_if_gdb6Fpv_b_ (0) + 129
 cccb1325 __1cUbugbuddy_segv_handle6Fi_v_ (5, 0, 8046540) + 89
 d12ef5ff __sighndlr (5, 0, 8046540, cccb129c) + f
 d12e44bb call_user_handler (5, 0, 8046540) + 2b8
 d12e4704 sigacthandler (5, 0, 8046540) + c2
 --- called from signal handler with signal 5 (SIGTRAP) ---
 d12f3b15 _lwp_kill (1, 5) + 15
 d12a8312 raise    (5) + 22
 d1086a5e g_logv   (cc116070, 8, cc116048, 8046c2c) + 2aa
 d1086b2d g_log    (cc116070, 8, cc116048, cc11603c, 132, cc115ff8) + 25
 cc10ed9a camel_url_new (8120318, 0) + 5a
 cb4b3bc0 org_gnome_exchange_owa_url (810d020, 8046cfc) + 38
 cc37f498 epl_invoke (810d020, 8265610, 8046cfc) + 54
 cc37f1a8 e_plugin_invoke (810d020, 8265610, 8046cfc) + 2c
 cc3754eb ech_config_widget_factory (8272990, 82a3d10, 83a59e8, 0, 8264f18) + 5f
 cc374163 ec_rebuild (8272990) + 2e3
 cc374c4b e_config_create_widget (8272990) + 127
 cc374d19 e_config_create_window (8272990, 0, cb462474) + 21
 cb3fb139 em_account_editor_construct (826a400, 0, 1, c72e25b0) + 435
 cb3f6174 em_account_editor_new (0, 1, c72e25b0) + 34
 c72e1c02 startup_wizard (810cfa0, 828cc08) + 6e
 cc37f498 epl_invoke (810cfa0, 81259e0, 828cc08) + 54
 cc37f1a8 e_plugin_invoke (810cfa0, 81259e0, 828cc08) + 2c
 cc37a32f emph_event_handle (80c3e60, 8124748, 80e13c0) + 33
 cc37a238 e_event_emit (80c3e60, 8068534, 828cc08) + f0
 0805e84d e_shell_attempt_upgrade (80bb3b0) + 431
 0805e165 e_shell_construct (80bb3b0, 8068660, 0) + a5
 0805e27f e_shell_new (0, 80471e4) + 27
 08066ea9 idle_cb  (0) + 169
 08066985 show_development_warning (804738c, 8047268, d13fb7d8, 0, cccb129c, 0) + 321
 080675a9 main     (1, 80472ac, 80472b4) + 3c5
 0805c046 _start   (1, 80473f4, 0, 80473fe, 8047442, 804745b) + 7a


Other information:
Comment 1 Jeff Cai 2008-01-31 10:11:08 UTC 
This is still a critical warning. When you work on a new feature, you should not introduce new critical warnings.
Comment 2 Jeff Cai 2008-02-01 10:39:23 UTC 
Created attachment 104183 [details] [review]
check the parameter before calling camel_url_new
Comment 3 Srinivasa Ragavan 2008-02-01 15:11:10 UTC 
Commit to trunk.
Comment 4 Jeff Cai 2008-02-02 00:58:33 UTC 
committed to trunk
Comment 5 C de-Avillez 2008-03-07 10:13:30 UTC 
marking fix as committed, since Jeff did the commit already (and the bug is already marked fixed).
Comment 6 Milan Crha 2008-09-15 09:45:26 UTC 
*** Bug 510557 has been marked as a duplicate of this bug. ***