This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: RE: ctrl-c in GDB
- From: "Vikas K. Prasad" <vikas dot prasad at ittiam dot com>
- To: <ecos-discuss at sources dot redhat dot com>
- Cc: "Vikas K. Prasad" <vikas dot prasad at ittiam dot com>,"Gary Thomas" <gary at mlbassoc dot com>
- Date: Sun, 3 Oct 2004 12:40:11 +0530
- Subject: RE: [ECOS] RE: ctrl-c in GDB
Gary,
Thank you for pointing it out. But fundamentally 0x18 interrupt
itself was not being hit.
However, I debugged from start and it was hanging near cache
enable macros. So, I got the ctrl-c to work in gdb after disabling
it. (Need to figure out why). Also, I wrote a 2 thread program
(with eCos) and got it to print on the gdb screen.
Thanks to Nick/David and all for the help.
I still have some problems wrt to 'info threads', mailbox etc.
(I think I will have to enable 'CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT'
in my redboot for the former RMT error).
I will try the 'ecos tests' (although I am using this for the first
time).
I will look into these and seek help depending on how it goes.
Regards,
Vikas
-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: Friday, October 01, 2004 5:05 PM
To: Nick Garnett
Cc: Vikas K. Prasad; David Brennan; ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] RE: ctrl-c in GDB
On Fri, 2004-10-01 at 03:04, Nick Garnett wrote:
> "Vikas K. Prasad" <vikas.prasad@ittiam.com> writes:
>
> > David/Nick,
> >
> > I tried that but did not work for me. However, one interesting
> > observation is that after loading the program (without ecos
> > but, redboot is present), I put a breakpoint at 0x18 (IRQ) -
> > and it did not hit! I am now suspecting if there is a more
> > fundamental step that is missed? Can you please give some
> > clues?
>
> As I said before, it looks like interrupts are not getting enabled
> somewhere.
Even more important is the statement above:
"without eCos but RedBoot is present"
If the program being run is not an eCos program, then that program
will be responsible for everything that eCos does to make ^C work.
These steps include (possibly not exhaustive):
* Setting the port to handle Rx interrupts
* Trapping the interrupt
* Calling RedBoot interface to process the character to check
for the presence of ^C
It certainly does not happen by magic and any program which expects
it to work needs to support the infrastructure to make it so.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss