Re: [ECOS] Tracing and Debug

[Jonathan Larmour <jlarmour@redhat.co.uk>]

Fabrice Gautier wrote:
> 
> > From: Jonathan Larmour [ mailto:jlarmour@redhat.co.uk ]
> > Fabrice Gautier wrote:
> > > Init device '/dev/ttydiag'
> > > Init tty channel: 27E6C
> > > Init device '/dev/haldiag'
> > > HAL/diag SERIAL init
> > > Init device '/dev/ser0'
                  ^^^^^^^^^^^

> > > Set output buffer - buf: 296C4 len: 512
> > > Set input buffer - buf: 298C4 len: 512
> > > ASSERT FAIL: <1>intr.cxx            [ 426] void
> > Cyg_Interrupt::attach()
> > > Interrupt vector not free.
> >
> > And here is your problem. The serial drivers have been
> > enabled, but this is
> > conflicting with the external break support because both want to put
> > interrupt handlers on the serial line. You cannot have both.
> 
> Hum...
> 
> So I shouldn't have HAL/diag serial device driver
> enabled(CYGPKG_IO_SERIAL_HALDIAG) when i include the GDB stubs in HAL with
> GDB external break support (CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS and
> CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT) ?

No, that HALDIAG driver should be enabled. But from the mention of
/dev/ser0 above, this indicates you have the "real" serial driver enabled,
and that is what conflicts with break support, i.e.
CYGPKG_IO_SERIAL_ARM_PID and CYGPKG_IO_SERIAL_ARM_PID_SERIAL0.

> But I don't see why the problem only occurs when I enable tracing? I seemed
> to run fine before.

It wasn't tracing that exposed this - it was assertions, which is default
enabled when tracing is enabled (although you can disable it).
 
> (I will check again for the other building problem - and perhaps will try
> the cvs stuff once I found any good cvs tool for Windows)

Don't forget to look at the links referenced from
http://sources.redhat.com/ecos/anoncvs.html if you haven't already.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault