Target reboots during driver debug

One of the docs says limited on-chip address trace should be available to me without an additional license. If so, has anyone used this?

Other debuggers have features like stack unwinding, stack limits checking. Any of this available to me?

I see in the default link/init, registers are defaulted to 0xdeadbeef and the data areas are randomly sprinkled with these markers. Is there any reasoning or description telling me where these were placed?

What does the debug level setting -g3 do for me. I did not see any difference.

thanks