RE: [ECOS] CYG_TRACE thread safe?

["Trenton D. Adams" <tadams at extremeeng dot com>]

Oops, forgot the cc once again.  To early in the morning I guess.

I updated to latest CVS yesterday.  I set it to compile over night, and
when I get back this morning, it doesn't freeze anymore.  Where do I get
the list of changes in the last couple of weeks to the eCos sources?

  > -----Original Message-----
  > From: jlarmour@cambridge.redhat.com 
  > [mailto:jlarmour@cambridge.redhat.com] On Behalf Of Jonathan Larmour
  > Sent: Thursday, July 12, 2001 8:53 AM
  > To: Trenton D. Adams
  > Subject: Re: [ECOS] CYG_TRACE thread safe?
  > 
  > 
  > "Trenton D. Adams" wrote:
  > > 
  > >   > My theory is that the ethernet hardware will have been
  > >   > configured to generate interrupts when its ready to
  > >   > transmit, or other status events. But diag output is done
  > >   > with interrupts disabled. Look at the driver code for your
  > >   > ethernet card to see how it works with interrupts.
  > >   >
  > > Oh, one other thing.  Does it disable interrupts just during the 
  > > CYG_TRACEx call?
  > 
  > Yes.
  > 
  > >  If so, I should probably use diag_printf () in between #ifdef 
  > > CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT and #endif right?
  > 
  > Worth a go.
  > 
  > 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 Come to the Red Hat 
  > TechWorld open source conference in Brussels!
  > Keynotes, techie talks and exhibitions    
  > http://www.redhat-techworld.com/
  >