>on a 3.5 Debug ROM (DR4) i see this error: "DataMgr.c, line 5462: Err
>insertion sort".
This is an error message from DmQuickSort, but DmInsertionSort could
generate the same error in the same circumstances. (Looks like somebody
copied and pasted the error message text, oops.)
The situation is different on various roms. However, the triggers for this
error are the same across versions.
There are two things that could cause this message from DmInsertionSort or
DmQuickSort:
- database is read-only
- database isn't a record database
In 3.5 release roms, you get an error code returned to your app.
In 3.5 debug roms, you get the fatal alert and then an error code returned
if you hit Continue.
In 3.3 you always get the fatal alert on both release and debug roms
In 3.2 you always get the fatal alert on both release and debug roms
In 3.1 you get the error code returned
In 3.0 you get the error code returned
I didn't look in 2.0 or 1.0.
The 3.5 behavior is what we in general would intend in a situation like
this, where the release rom should quietly bail and do nothing, hoping that
the app isn't in the process of going down in flames, while the debug rom
should immediately tell the developer that there's a fundamental problem
with the way the routine is being called or with the state of the world.
Hope this helps -
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
