Topic : Kernel debug in Ride7?

Forum : 8051

Original Post
Post Information Post
September 21, 2010 - 8:55pm
Guest

Ride6 has a handy check box to enable the kernel debug features. No such check box in Ride7. How do I enable kernel debug via Ride7?
Replies
Post Information Post
+1
0
-1
September 22, 2010 - 9:39am
Raisonance Support Team

Hi,

This is not yet supported in Ride7, and we are in the process of evaluating porting it from Ride6 to Ride7.

How useful would this feature be to you? Do you think this has a good value for 8051 developers?

Regards,
+1
0
-1
September 22, 2010 - 12:14pm
Guest

The kernel debug capability is invaluable. Otherwise I would be blind with respect to the kernel. I'm considering running the debug version always so that the call to kr_trap can be used to reset the processor. I would only turn it off if resources became sufficiently constrained.

For now I have saved backup copies of the libraries and renamed d_krxs.lib to krxs.lib.

I would recommend it be kept on the list to port but assigned a low priority.

Regards,
Chris
+1
0
-1
January 19, 2011 - 1:02am
Guest

With the last update to the 8051 tools I seem to have lost the debug version of the kernel libraries (e.g., d_krxs.lib). This is a problem.

Now I can not do the previously mentioned work-around (renaming d_krxs.lib to krxs.lib) which causes 2 problems:
- I have no idea when the KR-51 routines fail (with debug, conveniently redirected to KR_TRAP function)
- There is a symbol in the non-debug kernel libraries that causes a duplicate symbol on linking - SPX(DEFAULT_SPX)

Any reason I can not remove the DEFAULT_SPX module from krxs.lib? At least that gets rid of the duplicate symbol and I can link.

I also would like the debug library back. Please.

version 6.8.10.30