There was a small change in the file pc386.in that i made to get qemu to
connect to gdb, but gdb can't seem to find the rtems kernel binaries.

The change was to add GDBARGS = -s if -G option is specified.

Thanks,
Sree


On Sun, Jul 28, 2013 at 2:56 PM, Joel Sherrill <joel.sherr...@oarcorp.com>wrote:

>  Then it should start qemu with the right arguments to so it starts in gdb 
> server. You will need to start gdb in another window and attach with a 
> command like target remote :1234... From memory but that should be close.
>
> You can always check the qemu docs to get the port number but the simulator 
> is separate from gdb so you need to test it as an external target.
>
> Sree harsha <sreeh...@buffalo.edu> wrote:
>
>
>  It is for pc386 to test the globaledf scheduler
>
>
>  Sent from my Verizon Wireless 4G LTE Smartphone
>
>
>
> -------- Original message --------
> From: Joel Sherrill <joel.sherr...@oarcorp.com>
> Date: 07/28/2013 2:09 PM (GMT-05:00)
> To: Sree Harsha Konduri <sreeh...@buffalo.edu>
> Cc: rtems-devel@rtems.org
> Subject: Re: rtems-testing with gdb option
>
>
> Depends on the simulator if that mode is supported. It is for simulators you 
> run in a separate window from the gdb session.
>
> Which simulator?
>
> Sree Harsha Konduri <sreeh...@buffalo.edu> wrote:
>
>
>  Hello,
>
>  The rtems-testing module is provided with a -G option to put the
> executable to run in gdb mode, but this is not the case when we run it with
> -G. Is there something i am missing, can someone help me on this?
>
>  Thanks,
> Sree
>
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel

Reply via email to