Debugging with Eclipse

[Mohammed Khoory]

I think the problem isn't that the output is being eaten by Eclipse, in fact
I think the output is showing up fine because I get messages like "Connected
to the simulator.".. it's the debugger pausing for unknown reasons every
3000 cycles. After the first 3000 cycles, the RTEMS program is still in the
"zerobss" startup routine. If you notice in the debugging perspective, you
can pause the thread and resume it. It will always pause in the same places
everytime you run it no matter how long you wait, which seems odd if you ask
me. 
 
Is it possible to simulate an RTEMS image built with sis or leon3 with qemu?
I haven't seen any articles talking about it. I'm eventually going to switch
to TSIM though.

I'll keep messing around, see what I can find.

> -----Original Message-----
> From: Joel Sherrill [mailto:Joel.Sherrill at OARcorp.com]
> Sent: Wednesday, February 06, 2013 12:41 PM
> To: Mohammed Khoory
> Cc: rtems-users at rtems.org
> Subject: Re: Debugging with Eclipse
> 
> Since you mentioned "tar Sim" I think what you are seeing is what I asked
> about last week. Apparently Eclipse eats the console output for the gdb
> simulators. If you use an external simulator like qemu or tsim, the output
will
> show up in the window you started the simulator in.
> 
> If there is a solution, no one who answered last week knew it. I have been
> meaning to ask about this on the gdb mailing list.
> 
> --joel
>