bluemoon wrote:rdos wrote:Yes, but it is better to have the symbols in a separate file rather than in the kernel image itself.
I suppose you know that the symbols & debug info can be strip into another file.
I can't believe I am saying this, but I agree with rdos (Hell froze over? haha)
This has been a default/feature/whatever of microsoft compiliers/linkers for a while. They use a seperate file (*.pdb) that contains the debug info. This has some advantages, if your kernel code has all of 1-3 extra lines of code, its easy to ignore missing debug info, and then just delete them from releases. This CAN be easier to maintain (but is not be default). It also has the advantage of giving you, the developer, a realistic idea of the size of a binary file (ie. without debugging info) And this plays nice with both local and remote debugging techniques.
However, this does require extra code to load the debug info when it is present, and may not be feasible in early stages of development.
So, both ways work, both ways make "sense" and both ways have pros/cons. This really comes down to personal preference/experience.
- Monk