Re: [ECOS] More information on crash with CVS sources

["Lewin A.R.W. Edwards" <larwe@larwe.com>]

Hi Jonathan,

> > By stepping the program, I've subsequently found that my crash problem
> > (with anoncvs app running on top of 1.3.1 stubs) occurs when the app
> > first tries to printf something. I guess I can fix this by disabling
> > virtual vectors in the app?
> > But it still doesn't explain why I'm not able to run an app on top of
> > the anoncvs-built stubs.
>
>Jesper just checked in a whole bunch of changes to do with virtual vectors.
>When does your anoncvs checkout date from?

It's from... hmmm... last Friday or Thursday maybe (I'm booted to Windows 
right now... can't check). I'll update tomorrow morning then look into a 
patch Gary sent me.

However, in further news, I built a little test proglet that consists of 
just a cyg_user_start that does a printf [and nothing else] and a main() 
that also does a printf.

In 1.3.1, it is seemingly not necessary to explicitly create and start a 
thread. cyg_user_start enables interrupts, and then control passes to 
main(). So my program at the moment runs in main() [since it was ported 
from a different OS].

When I compile the above test prog with anoncvs everything, I get the 
printf from cyg_user_start but not the one from main; after the printf("hi 
from cyg_user_start") I get an exception at 0xfffffffc. So I assume the 
1.3.1 behavior I describe above is no longer true and that I must 
explicitly start a thread for my main application task.

It doesn't completely explain why I can't get the anoncvs app to run on 
anoncvs stubs, though - I never even get the "new thread 0 created" message 
or the cyg_user_start message. Bizarre.
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."