#37 mged segfault

crash or data loss

#0 dotitles (overlay_vls=0xbffff020) at titles.c:263
263 bu_vls_printf(&path_lhs, "/%s",
DB_FULL_PATH_GET(&illump->s_fullpath,i)->d_namep); (gdb)
bt #0 dotitles (overlay_vls=0xbffff020) at titles.c:263
#1 0x080c9fe8 in refresh () at ged.c:1753
#2 0x080c76f9 in main (argc=2, argv=0xbffff1a4) at

When I was editing one multiply referenced object and
then did accept (the change was translation), istead of
both reference being translated on screen, only one was
translated and the other disappeared. When did 'B mast'
again, it was appearing OK again.

But shortly after that, during editing, the mged crashed
(without loss of data).


  • Sean Morrison

    Sean Morrison - 2005-12-29
    • labels: --> Geometry Editing
    • assigned_to: nobody --> brlcad
    • milestone: --> crash or data loss
  • Sean Morrison

    Sean Morrison - 2005-12-29

    Logged In: YES

    The command line will let you reference the same object multiple times in a
    single combination/region, though this practice is discouraged for various
    reasons. Was this what you were doing, or was it one object referenced in
    multiple combinations? I suspect it's the prior, which is a known issue with
    mged's drawing update.

    A simple workaround is to either create copies (so they have unique names at
    least within a single combination) or to create surrogate child combination
    that reference the same object. Both paths, of course, simply work around
    the problem by avoiding the multiple identically named references in a single
    combination. Again, it is a known limitation (though it 'should' raytrace/
    analyse correctly).

  • Lee Butler

    Lee Butler - 2006-01-11
    • status: open --> pending
  • Sean Morrison

    Sean Morrison - 2006-01-30
    • status: pending --> open
  • Sean Morrison

    Sean Morrison - 2006-01-30

    Logged In: YES

    Changed from pending to open to make the e-mails stop. Investigating why
    that particular crash happened still.

  • Sean Morrison

    Sean Morrison - 2006-02-04

    Logged In: YES

    The stack trace was very helpful. While the problem of multiply referenced
    objects is still problematic in mged, this particular crash has been fixed in the
    latest CVS. The multiply referenced object in a single combination causes a
    variety of problems (as you have noticed) with mged's state management.. best
    to avoid doing that (and instead make named or referenced copies) for the time

  • Sean Morrison

    Sean Morrison - 2006-02-04
    • status: open --> closed-fixed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks