Search Results
Search results 1-7 of 7.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Do you specify GCC option '-gdwarf-4' ? Since GCC11 DWARF5 is the default debug symbol format which is not yet supported by JLink/Ozone.
-
See also this post related to GCC11 defaulting to DWARF-5, too.
-
Glad to read that it's already on your page Thanks AlexD !
-
Hi, after migration to GCC11 for ARM Cortex-M watching member variables is not longer working (maybe other related features, too). As documented in the GCC11 release notes the default debugging format is now DWARF-5 which confuses Ozone. After switching back to DWARF-4 (specifying GCC option -gdwarf-4) it's working again. Any plans to add DWARF-5 support Best regards, HS2
-
@nino I'm aware that it's hard to find and fix something w/o a reproducible testcase.. I've added my findings to underline that it's a somewhat systematic and not a user specific problem. To be honest I can't remember if Ozone prompted for re-load before getting unresponsive on regaining focus after a longer period being idle in the background. I'll pay (more) attention and report back. Thanks !
-
Yes, I'm using the latest non-beta JLink package and also ensure Ozone is not running when installing JLink. No, as mentioned since it happens sporadically (and luckily not very often) I don't see how to provide a reproducible test case. I only know that wasn't the case in the past (1,2, .. ? versions before), my jdebug scripts are the same since a pretty long time. I can start a Ozone debug session and work with it, then I leave it running the target and go back to work on the sources. Then aft…
-
I've encountered the same issue. Ozone stucks sporadically e.g. after being idle a while and the process needs to killed. Ozone V3.20b on Win10x64