That crash appears to appear first in revision 140558 of kerext_process.c:
<http://svn.ott.qnx.com/view/product/trunk/services/system/ker/kerext_proces
s.c?annotate=140558>

Looks like ProcessDestroyAll() is asserting that the process to destroy has
no open fds. Which is done at line 314 in the current rev of
kerext_process.c


Mario Charest wrote:
> The machine crashed while booting with the message:
> 
> Crash[0,0] at kerext_process line 253.
> 
> Any clue?  I looked into the source ( yeah baby! ) but the target is 
> 6.3.0 and it seems the source have been updated since then ;-)
> 
> I have not ruled out hardware problem for the moment.
> 
> Mario
> 
> 
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post4648
> 

Attilla Danko wrote:
> That crash appears to appear first in revision 140558 of kerext_process.c:
Oops. 140448 is the *latest* revision with a crash() on line 253. The
earliest
is revision 123066.

Because that area of code is a big block of asserts, you need to know
exactly
which version of 6.3.0 (the exact rev number of kerext_process.c) since that
block of asserts shifts around from ref to rev. For example in 123066, line
253 is asserting the clobbert process must have zero active threads.