[Solved] 4.13 bug: Invisible Breakpoints

Go To Last Post
15 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Like several other users I'm experiencing the 'invisible breakpoint' bug in 4.13 (both build 522 and 524, duly reported to but so far not acknowledged by the development team).

The problem seems to be machine dependent - here only on one out of three computers AVRStudio shows this behaviour (all systems run XP SP2 with the current hotfixes installed).

Bug description:
- 'F9' or clicking the 'toggle breakpoint' icon will set a breakpoint, but the symbol doesn't show up in the side bar.

- Even though this 'invisible breakpoint' works, the associated 'Breakpoints and Tracepoints' window internally isn't activated - it is available in the UI window selection options, but will show the previous window's content or else stays empty when moved to a different location.

- 'Reload file' causes the symbol(s) of set breakpoints to appear once: toggling an individual breakpoint off and on makes it invisible again, but even after 'reloading' the breakpoint(s) won't show up in the 'Breakpoints and Tracepoints' window.

I'm wondering if there might be a common denominator for the systems which have this bug - .NET frameworks installed (#3 on the machine which has the bug), graphics driver (NVIDIA 93.71), whatever ... I'd appreciate any feedback and ideas.

[Edit] Changed tag line

Andreas

Last Edited: Mon. Feb 19, 2007 - 12:23 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Update:

Finally solved the 'invisible breakpoint' bug - it seems to be caused by leftover entries in the registry from previous AVRStudio (back to V. 3.56) and plugin installations.

This is what worked for me:

- De-install *everything* (AVRStudio, Plugins, WinAVR). *Don't* immediately re-install - been there, doesn't work
- Search the registry for 'Atmel', 'AVR' etc. Delete each and every key (not just entries under the keys) containing references to these criteria
- Re- install everything
- Delete all .aps files and re-create your projects

Andreas

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I my case, all I had to to is uninstall AVR Studio 4.13 and replying yes to the question "Do you want to delete all settings from the registries" during uninstall. Once AVR Studio 4.13 is reinstalled, I got proper breakpoint behavior.

Regards

Michel

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Unfortunately, all this does not work for me, breakpoints are still invisible. I still consider this being a bug. But unlike you, I do not use XP.

- Windows 2000 SP4, all patches applied
- AVR Studio 4.13, Build 524

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

In previous versions of AVRstudio I have found the Administrator and user login registry copies/versions are treated differently by the uninstall option. Since AVRstudio must be installed and uninstalled from an Administrator privilege account, only the registry copy from this account seems to clear correctly (I always used the actual Administrator account). If you ever ran AVRstudio from any other account that registry copy is not cleared and is left “dirty”. Maybe this has changed? Try uninstalling with the clear registry option, reinstalling and running from that same Win 2k Administrator privilege account. See if it solves your problem or not.

AVRstudio is one of a very few reasons why I still have Win 2k at all. Since I no longer let any Windows OS on the Internet ever and because its a single user computer, I just run everything in the Administrator account now. It goes against old habits, but it actually makes sense for my situation and I have not tangled with any AVRstudio registry issues since.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I tried the administrative account now, but it didn't change anything for me. Beside that, hitting Ctrl+F9 (Debug -> Next Breakpoint) with breakpoints set just crashes AVR Studio.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Mike makes a good point (thanks!) - to be able to access and clean out *all* (Atmel-related and others) registry entries, logged on with administrator privileges you can take ownership of the registry files (located in %systemroot%\system32\config\) - opens up grand new perspectives in regedit :) .

Note: This is a non-reversible process (short of an OS re-install) and of course also makes it even easier for each and every malware which happens to become active while an user with administrative rights is logged in to wreck havoc on the system.

[rant on]
In Ancient Rome, they had some rules for dealing with masons' and architects' (one and the same at that time) blunders: if the building the craftsman had erected happened to collapse afterwards, he was held responsible for the damage caused. If he couldn't pay, he was invited as a participant in the arena at the next 'munera' (the public games) instead, thereby serving the dual purpose of being removed as a public threat *and* providing entertainment for the audience.

Each time I have to spend hours to weed out 'bad' entries a program has left in the registry to get an application or the whole system working again, I tend to think of the programmer and good old Rome ... there's this floor mosaic in a north african villa portraying a culprit tied to a stake for easy access by the lions (very convenient, they may have had usability studies even in those days) ...
[rant off]

Andreas

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Spes vestri domus est in ordo in nostrum iter itineris

Lars Kvenild
Atmel Norway

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I lost the indication of breakpoints only after I installed AVR32 Studio recently. Has anyone else experienced this?

Tom

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Trym wrote:
Spes vestri domus est in ordo in nostrum iter itineris

Lars Kvenild
Atmel Norway

Hmm siger man sådan når man har fået for meget Myseost ??

/Bingo

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I've had similar problems installing on XP SP2, I followed the recommendations, and fully removed any trace of previous versions of Studio from the disk and registery, and then installed a fresh copy. This solved the problem for about a week, now the problem is back. It cannot display the breakpoints. I use Visual Studio .NET a lot, if this could cause conflicts?

Every time I upgrade Studio, I seem to take to steps forward, and two backwards. I should have learned my lesson, and stayed with 4.12

Colin

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Colin - did you perchance open an 'old' project file in your all-new Studio installation?

I'm always able to blow away the breakpoints by that technique ...

Andreas

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yep, you hit the nail on the head, thats exactly what I did. I have almost 100 projects I've been working on, and I went to look at an old version.

Thanks
Colin

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Alenze, is this problem actually solved (per your edited topic name)? Atmel hasn't released a new version yet that addresses it.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

'Solved' only in the sense of the above described workarounds - no official reaction by Atmel yet.

Andreas