Hi,
Sean has left the following comment at Crash our raytracer application
reliably http://www.google-melange.com/gci/task/view/google/gci2012/8018211:
backtrace
If rt actually crashed, you should be able to capture a stack trace. That
is a record of all the functions there were called at the time it crashed.
I won't have time to verify whether your description qualifies as a crash
for a day or two (maybe one of the other mentors can verify sooner), but a
crash log would be more direct evidence.
To get a crash log, just run rt from within a debugger. If you have a Mac,
crash logs are usually generated automatically when you get the dialog
to "send them in". If you have gdb (a debugger) or MSVC, you should be able
to get it to crash within the debugger and obtain a stack trace that way.
If you have *bomb.log files, that may be evidence as well (and may not,
depends on the content).
Greetings,
The Google Open Source Programs Team
---
You are receiving this message because you are subscribed to Crash our
raytracer application reliably.
To stop receiving these messages, go to:
http://www.google-melange.com/gci/task/view/google/gci2012/8018211.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
BRL-CAD Tracker mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-tracker
