I think you are right...  I became happy too soon.  The problem re-
appeared.  Thanks for the tip of paying more attention to strings.

I guess I will just have to carefully examine my entire code.  It is 
a difficult to trace since I only see the problem right at the end of 
a debug session when I press the kill button.  If I just normally 
exit my app the problem does not occur, but of course then the 
debugger is still running.  It is only when I try to stop the 
debugger that it occurs.

What makes this a bit more annoying is that afterwards I have to do a 
hard reset with loss of all data in order to recover POSE to a 
workable state.  And my app relies on several database files that 
needs to be loaded each time before I can commence testing.

Werner


--- In [EMAIL PROTECTED], "Dave Lippincott" <[EMAIL PROTECTED]> 
wrote:
> > A "bus error" means that the application accessed a memory 
location that
> is not in RAM or ROM, nor corresponds to a memory-mapped > hardware
> register.20.797: === ERROR:
> Not completely true.  A bus error is a generic memory error.  It 
just means
> the app access an area of memory it was not suppose to at that time.
> 
> I wouldn't settle for 'just gone'.  A bus error usually indicates 
your
> application has over-written another area in memory.  More often 
then not
> its from placing too many characters into a string that was not 
initialized
> with enough memory.  I'd double check your code in the area 
executed just
> before the error occurred.  Don't be satisfied with it just went 
away after
> I recompiled it.
> 
> ----- Original Message -----
> From: "wterreblanche" <[EMAIL PROTECTED]>
> To: "Palm Developer Forum" <[EMAIL PROTECTED]>
> Sent: Monday, June 23, 2003 7:10 AM
> Subject: Re: How do one locate the cause for this Bus error?
> 
> 
> > It seems that I finally managed to resolve this problem myself.
> > Basically all I've done was to select factory settings in CW9 for 
the
> > debugger settings.  Afterwards the problem was gone.  I'm not sure
> > which setting was the offending one and would still like to 
know...
> > but at least the problem is gone for now.
> >
> > Werner
> >
> > --- In [EMAIL PROTECTED], "Werner Terreblanche"
> > <[EMAIL PROTECTED]> wrote:
> > > My app has suddently started giving "bus error" messages in Pose
> > when I'm
> > > killing a CodeWarrior debug session.   When I run the app 
(without
> > using the
> > > debug option) then it runs fine and does not give an error.  
But as
> > soon as
> > > I try to debug I get this error only at the point where I kill 
the
> > debug
> > > session.  I can trace the source code right up to the point 
where
> > the last
> > > instruction in my AppStop() routine have been executed.  So it
> > really looks
> > > like the error occurs when the debugger is busy terminating.
> > >
> > > How do one find such an error?  I have spent my entire Sunday
> > afternoon and
> > > can still not figure out what to do.   I do not even know what
> > normally
> > > cause a bus error and why does it only happen at the end of a 
debug
> > a
> > > session?  Any tips of what to look out for would be greatly
> > appreciated.
> > >
> > > Here is an example what the last few lines that I see the log 
file
> > of POSE:
> > >
> > > 20.718: --- System Call 0xA39E: |-|-|-|-|-WinRGBToIndex.
> > > 20.718: --- System Call 0xA3E0: |-|-|-|-|-|BmpGetColortable.
> > > 20.718: --- System Call 0xA375: |-|-|-|-|-|BltFindIndexes.
> > > 20.718: --- System Call 0xA39E: |-|-|-|-|-WinRGBToIndex.
> > > 20.718: --- System Call 0xA3E0: |-|-|-|-|-|BmpGetColortable.
> > > 20.718: --- System Call 0xA375: |-|-|-|-|-|BltFindIndexes.
> > > 20.718: --- System Call 0xA035: |-|-|-|-|-MemPtrUnlock.
> > > 20.718: --- System Call 0xA061: |-|-|-|-|-DmReleaseResource.
> > > 20.797: === ERROR:
> > >
> > 
**********************************************************************
> > ******
> > > ****
> > > 20.797: === ERROR: MyApp (1.0) just read from memory location
> > 0x8003D261,
> > > causing a bus error.
> > >
> > > A "bus error" means that the application accessed a memory 
location
> > that is
> > > not in RAM or ROM, nor corresponds to a memory-mapped hardware
> > register.
> > > 20.797: === ERROR:
> > >
> > 
**********************************************************************
> > ******
> > > ****
> > >
> > > Best regards
> > > Werner Terreblanche
> > >
> > >
> > > --
> > > For information on using the Palm Developer Forums, or to
> > unsubscribe, please see http://www.palmos.com/dev/support/forums/
> >
> >
> > --
> > For information on using the Palm Developer Forums, or to 
unsubscribe,
> please see http://www.palmos.com/dev/support/forums/
> >
> 
> 
> -- 
> For information on using the Palm Developer Forums, or to 
unsubscribe, please see http://www.palmos.com/dev/support/forums/


-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/support/forums/

Reply via email to