RE: [ECOS] Continuous Loop between delay_us and redboot\GDB

["Douglas Bush" <dbush at extremeeng dot com>]

Thanks.

However, I'm not calling it anywhere in my code after initialization. I
suppose I could clip the value when it gets called, just to see what's
causing the fault.... Or even flag unusually large values when it gets
called.

The only thing I know for sure is that the driver isn't re-initializing.
Sometimes it even continues to run even though GDB isn't operating.  (I
learned this with an ICE.)

-----Original Message-----
From: jlarmour@cambridge.redhat.com
[mailto:jlarmour@cambridge.redhat.com] On Behalf Of Jonathan Larmour
Sent: Wednesday, February 27, 2002 4:15 PM
To: Douglas Bush
Cc: eCos Discussion List
Subject: Re: [ECOS] Continuous Loop between delay_us and redboot\GDB

Douglas Bush wrote:
> 
> Folks,
> 
> I?m having trouble identifying what?s killing a device driver.
> 
> When the driver does die, the processor goes into what appears to be a
> continuous loop in delay_us \ hal_clock_read, which is being called
from
> redboot\GDB.

I recall that it is easy to cause an overflow in delay_us if you pass it
a
value that's too large.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223)
271062
Maybe this world is another planet's Hell -Aldous Huxley ||
Opinions==mine


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss