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 309382 - dia crashes on neworthconn_update_data()
dia crashes on neworthconn_update_data()
Status: RESOLVED DUPLICATE of bug 309381
Product: dia
Classification: Other
Component: general
CVS head
Other Linux
: Normal normal
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2005-07-03 14:25 UTC by Nguyen Thai Ngoc Duy
Modified: 2005-07-10 16:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nguyen Thai Ngoc Duy 2005-07-03 14:25:40 UTC 
The last bug i found when trying dia-cvs :)


Program received signal SIGSEGV, Segmentation fault.
ddisplay_add_update_pixels (ddisp=0x9797eb0, point=0x28, pixel_width=5,
pixel_height=5)
    at display.c:332
332       rect.left = point->x - size_x/2.0;
(gdb) bt

+ Trace 61577

  • #0 ddisplay_add_update_pixels
    at display.c line 332
  • #1 diagram_add_update_pixels
    at diagram.c line 758
  • #2 connectionpoint_add_update
    at connectionpoint_ops.c line 85
  • #3 object_add_updates
    at object_ops.c line 51
  • #4 textedit_remove_focus_all
    at textedit.c line 50
  • #5 diagram_remove_all_selected
    at diagram.c line 603
  • #6 dia_layer_select_callback
    at layer_dialog.c line 272
  • #7 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 gtk_item_select
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ?? 






Comment 1


Hans Breuer





          2005-07-10 16:50:27 UTC
        



This may some side effect of
http://bugzilla.gnome.org/show_bug.cgi?id=309381
which just got fixed. It was writing to memory it
did not own. Not able to reproduce this one.

Tentative duplicate.

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