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 470782 - crash in Dia Diagram Editor: Abriendo un documento ge...
crash in Dia Diagram Editor: Abriendo un documento ge...
Status: RESOLVED DUPLICATE of bug 443651
Product: dia
Classification: Other
Component: python
unspecified
Other All
: High critical
: ---
Assigned To: Hans Breuer
Hans Breuer
Depends on:
Blocks:
 
 
Reported: 2007-08-27 18:31 UTC by Nicolás Mosconi
Modified: 2007-10-27 11:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
The autogenerated diagram (115.88 KB, text/xml)
2007-09-13 00:04 UTC, Nicolás Mosconi 		Details

Description Nicolás Mosconi 2007-08-27 18:31:48 UTC 
Version: @0.96.1@

What were you doing when the application crashed?
Abriendo un documento generado por autodia


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-bootsplash #3 SMP Sun Jul 15 21:28:30 ART 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Aqua-Glade_PNG

Memory status: size: 56209408 vsize: 56209408 resident: 43532288 share: 14737408 rss: 43532288 rss_rlim: 4294967295
CPU usage: start_time: 1188239114 rtime: 225 utime: 201 stime: 24 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

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

+ Trace 158248

Thread 1 (Thread -1224894272 (LWP 8499))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/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/i686/cmov/libc.so.6
  • #6 abort
    from /lib/i686/cmov/libc.so.6
  • #7 __assert_fail
    from /lib/i686/cmov/libc.so.6
  • #8 diagram_remove_ddisplay
  • #9 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #10 diagram_load
  • #11 file_open_callback
  • #12 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_override_class_closure
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #17 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_override_class_closure
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #24 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 main
  • #0 __kernel_vsyscall 






Comment 1


Nicolás Mosconi





          2007-08-30 22:34:16 UTC
        



El error ocurrió al abrir un archivo que contenía un diagrama dia pero cuya extensión era .xml






Comment 2


Lars Clausen





          2007-09-12 20:51:23 UTC
        



Could you attach the diagram to this bug so we can try it out?  Even if this is corrupted diagram created by AutoDia, it should not crash Dia.  Does it happen if the extension is not .xml?  Apparently, XML files are grabbed by a Python importer.






Comment 3


Nicolás Mosconi





          2007-09-13 00:04:54 UTC
        



Created attachment 95487 [details]
The autogenerated diagram






Comment 4


Nicolás Mosconi





          2007-09-13 00:07:17 UTC
        



"Does it happen if the extension is not .xml?"
No, if i rename the file as autodia.dia it works ok






Comment 5


Lars Clausen





          2007-09-13 20:14:28 UTC
        



Reassigned to python component since it appears Python is grabbing the file and dying.






Comment 6


Hans Breuer





          2007-09-15 19:22:15 UTC
        



xml files are indeed processed by doxrev.py, but the file here does not crash on me. Instead it simply gives:

PyDia Error (diamodule.c:277):
<exceptions.NameError instance at 0x02DB1F30>
Traceback (most recent call last):




+
Trace
    163164






    

  • 
          File "D:\graph\dia2\python\doxrev.py",
          line 488
            in import_file

    • 

  • 
          File "D:\graph\dia2\python\doxrev.py",
          line 401
            in GetClasses

    • 







    
except xml.parsers.expat.ExpatError :

Looks like expat (the xml parser) does not like it for some reason. But also in the stack trace above there is no Python involved. Did you open the file in a specific manner (drag&drop, from command line)?






Comment 7


Nicolás Mosconi





          2007-09-16 19:45:40 UTC
        



yes, now i remember.
I open the file as a dox2UML(.xml) file. That cause the crash.

Sorry for my english.







Comment 8


Hans Breuer





          2007-10-27 11:46:30 UTC
        




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