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 311916 - Evolution crashed because of bold text - In pango library
Evolution crashed because of bold text - In pango library
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[groupwise]
Depends on:
Blocks: 318200
 
 
Reported: 2005-07-29 05:00 UTC by Nagappan Alagappan
Modified: 2013-09-13 00:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Nagappan Alagappan 2005-07-29 05:00:43 UTC 
Distribution/Version: SuSE 9.3

In Evolution 2.3.6 build dated 27-July-2005 for SuSE 9.3 platform, when we have
a calendar item with lengthy text and if the text state is in bold, then
Evolution crashes. Stack trace shows that the crash is due to pango library.

+ Trace 62054

Thread 3 (Thread 1111030704 (LWP 10803))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 pthread_cond_timedwait
    from /lib/tls/libpthread.so.0
  • #5 _wapi_handle_check_share
    from /usr/lib/libmono.so.0
  • #6 _wapi_handle_timedwait_signal_handle
    from /usr/lib/libmono.so.0
  • #7 _wapi_handle_wait_signal_handle
    from /usr/lib/libmono.so.0
  • #8 WaitForSingleObjectEx
    from /usr/lib/libmono.so.0
  • #9 ves_icall_System_GC_WaitForPendingFinalizers
    from /usr/lib/libmono.so.0
  • #10 ves_icall_System_Threading_Thread_Thread_internal
    from /usr/lib/libmono.so.0
  • #11 _wapi_timed_thread_exit
    from /usr/lib/libmono.so.0
  • #12 GC_start_routine
    from /usr/lib/libmono.so.0
  • #13 start_thread
    from /lib/tls/libpthread.so.0
  • #14 clone
    from /lib/tls/libc.so.6 






Comment 1


Owen Taylor





          2005-07-29 12:24:10 UTC
        



You need to provide a backtrace with debugging symbols; there is no way
I can proceed further with the information provided here.

I also need to know exactly what Pango version is involved - either the
released version or the date at which it was built from CVS.
("Evolution 2.3.6 build dated 27-July-2005" means nothing to me)







Comment 2


Nagappan Alagappan





          2005-07-29 12:43:58 UTC
        



Owen Taylor;

0x4126ef00 in pango_log2vis_get_embedding_levels (str=0x8679638, len=3,
pbase_dir=0x8612558,
    embedding_level_list=0x8568740 "@xGAXqg\b\020") at fribidi.c:595
595         for (pp = type_rl_list->next; pp->next; pp = pp->next)

gdb trace




+
Trace
    62071






Thread 3
          (Thread 1111047088 (LWP 9484))


    

  • 
#0
??

    • 

  • 
#1
??

    • 

  • 
#2
??

    • 

  • 
#3
??

    • 

  • 
#4
pthread_cond_timedwait

    
                from
                /lib/tls/libpthread.so.0

    

    • 

  • 
#5
_wapi_handle_check_share

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#6
_wapi_handle_timedwait_signal_handle

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#7
_wapi_handle_wait_signal_handle

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#8
WaitForSingleObjectEx

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#9
ves_icall_System_GC_WaitForPendingFinalizers

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#10
ves_icall_System_Threading_Thread_Thread_internal

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#11
_wapi_timed_thread_exit

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#12
GC_start_routine

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#13
start_thread

    
                from
                /lib/tls/libpthread.so.0

    

    • 

  • 
#14
clone

    
                from
                /lib/tls/libc.so.6

    

    • 









Hope this helps you to debug the issue further.

Chen: Maybe you can add more comment as you have used this in Evolution.






Comment 3


Owen Taylor





          2005-07-29 13:56:01 UTC
        



Looks like memory corruption to me. There's no way that 
without memory corruption pango_log2vis_get_embedding_levels() could
be crashing when analyizing the string "...".

Reassigning to evolution (could also be a an "e_text" bug, so a gal bug)

Tools like valgrind could help tracking down the issue.






Comment 4


Chenthill P





          2005-08-22 18:29:23 UTC
        



This part of the code no longer is executed and i don see the crash any more
even with it. It will be enabled once a Gw server fix is in. 






Comment 5


Chenthill P





          2005-12-21 14:34:45 UTC
        



This not present anymore.