Here on Peg2 I set two break points in one file. The first one at main, the second at line 364.
GDB stops at the first break point as expected. But after pressing c for continue the program runs without any further breaks until termination.
The second break point is completely ignored.
Is this an internal AOS4-GBB-Problem or did I make sth. wrong/misunderstood sth.?
Any hints/help highly appreciated for how becoming GDB to work with more than one breakpoint!
I'm at an end. I've uploaded TaskView at OS4Depot, but I discovered right after uploading that the program crashes at startup. It didn't do so when developing and compiling into a debug version (I wouldn't have released it when it did, now would I?).
After checking the released version of my program TaskView (OS4Depot), I found that it crashes (with a GR) at starting time, before the window opens.
The GR mentions that 'Redzone was damaged'.
What exactly does this mean (should I FRSFM?)?
I have a real strange & frustrating experience here:
While trying to iron out another problem, i suddenly got a lot of undefined references to a number of variables and structures i had declared (say myvar is one of them) as extern in my gui-protos.h file.
I deleted them there and added them to gui.c where i have my main() function.
The problem did not disappear. I tried at different places with regard to my includes to no avail. I then just put the declaration as well in gui-protos.h
Maybe now that DBG is said to be operational again i will encounter less problems.
However i have lost hours(days really) on finding a bug that was just a print statement in
a backfill hook function.
I also had trouble with printstatements (PutStr) in the library and interface closing code.
In code using the pipe functions i learned that PutStr() is safe, and Printf freezes the system. How about the experience of old hands?