REBOL 3.0

Comments on: How to debug and report a crash

Carl Sassenrath, CTO
REBOL Technologies
12-Oct-2009 18:34 GMT

Article #0269
Main page || Index || Prior Article [0268] || Next Article [0270] || 1 Comments || Send feedback

When a crash occurs in R3 it can be difficult to know what caused it (so you can report it as a bug.)

It is possible to obtain a crash dump from R3 when a crash happens. Here's how to enable it:

>> secure [debug allow] 
>> evoke 'crash-dump

Now, if a crash occurs, you will see internal information displayed on the console. It includes a stack dump that should help you determine where the crash happened.

Try to get the crash to occur in just a few lines of code, so you can report it as a bug. Do not report just "my code crashed". That is not helpful.

If necessary, we can improve on the crash dump output in the future to provide more information about state of the system as of the crash.

1 Comments

Comments:

Maxim Olivier-Adlhoch
12-Oct-2009 16:51:29
WOW !

this is one of the most interesting new thing to come out of the "Carl's secret R3 file" for a while. :-)

You should start a new blog called: "Carl's magic tricks"

Where you just dump neat tricks, code patterns, and hidden, new or not yet publicized R3 features. it would have quite a following.

Post a Comment:

You can post a comment here. Keep it on-topic.

Name:

Blog id:

R3-0269


Comment:


 Note: HTML tags allowed for: b i u li ol ul font span div a p br pre tt blockquote
 
 

This is a technical blog related to the above topic. We reserve the right to remove comments that are off-topic, irrelevant links, advertisements, spams, personal attacks, politics, religion, etc.

REBOL 3.0
Updated 23-Jun-2017 - Edit - Copyright REBOL Technologies - REBOL.net