Menu
Logged-In As
ACCOUNTNot Logged In
Crash MGED reliablyBRL-CAD
Status: ClosedTime to complete:
48 hrs
Mentors: Sean
BRL-CAD's primary geometry editing tool is called 'mged'. What's more frustrating than software crashes? We put a lot of emphasis on developing quality software so see if you can find a problem.
Find a way to crash mged reliably. You must compile our latest Subversion sources, run mged, and keep track of steps taken that cause a crash. If you can provide a stack trace, even better. You must submit specific conditions and steps that will reliably and reproducibly cause a crash.
It must be a bug that is NOT already documented in our BUGS or Sourceforge bug tracker nor be a bu_bomb() graceful termination. It might help to become minimally familiar with how to run mged as the interface is not at all newbie-friendly.
References
- http://brlcad.svn.sourceforge.net/viewvc/brlcad/brlcad/trunk/BUGS
- https://sourceforge.net/tracker/?group_id=105292atid=640802source=navbar
- http://brlcad.org/wiki/Documentation
Uploaded Work
| File name/URL | File size | Date submitted | |
|---|---|---|---|
| BRL-CAD crash.mov | 5.9 MB | December 05 2012 01:22 UTC | |
| mged-710-bomb.log | 2.0 KB | December 05 2012 02:29 UTC |
I would like to work on this task.
This task has been assigned to Chris Kloehn. You have 48 hours to complete this task, good luck!
Is this the proper link to the download I need to compete this task?
http://sourceforge.net/projects/brlcad/files/latest/download?source=files
For this task, that link will certainly work since it was the last binary release. Since you're on Mac OS X, if you can get MGED to crash, a detailed log should be created for your automatically. Be sure to include that along with steps that reliably reproduce the crash.
Thank you, Ill get right on the quality assurance, but what would you like me to do in the case that your program doesnt crash?
We're not foolish enough to think that our software won't crash. You might have to hunt for a couple hours, but finding a crash should be possible. I get it to crash regularly just through normal use, without even trying.
That said, this task is like our spelling mistake tasks. If you cannot get it to crash, then you'll have to release the task so someone else can try.
The work on this task is ready to be reviewed.
This one technically qualifies as a graceful abort (the bu_bomb() that is referred to in the description), but you should send in a crash log anyways. MGED takes a couple seconds to shut down because it's writing out a bomb log. Find it and submit.
It'll probably either be within the application bundle. Right click the BRL-CAD application icon, show contents, and traverse to Contents, then Resources. There should be several files named mged-#####-bomb.log -- submit one of them..
The deadline of the task has been extended with 1 days and 0 hours.
Found the files, submited them seconds ago. Thanks for extending deadline just in case.
Congratulations, this task has been completed successfully.
As GCI comes to a close, we wanted to take the time to say THANK YOU for all your efforts. This comment interface closes after GCI is over, so you're encouraged to join our mailing list where we'll be announcing contributions from GCI participants like yourelf over the upcoming months:
https://lists.sourceforge.net/lists/listinfo/brlcad-news
If you've provided your full name, we'll be sure to credit you in our authorship documentation and you'll see your name in a future announcement. If you contact us at devs@brlcad.org or via IRC, we'll even let you know when your work is integrated and follow up with updates. You're welcome and encouraged to contact us any time, especially if you have a question about how to continue participating in Open Source after GCI is over, but even if just to keep in touch. Note that ongoing participation in Open Source is one of the most impressive skills to have on your resumé. Take care, be well, and thank you again!