On Tue, Nov 05, 2013 at 12:41:12PM +1300, Andrew McLaren wrote:
> Thanks Daniel and Eric.
>
> All working, and another (little) frustration removed.
>
> Just out of curiousity, what home location does Mspdebug pick up its
> .mspdebug init file from on XP? It doesn't appear to be the normal
> User
in my working directory, which is perfect for what I need.
Regards
Andrew
-Original Message-
From: Daniel Beer [mailto:dlb...@gmail.com]
Sent: Monday, 4 November 2013 4:35 p.m.
To: Andrew McLaren
Cc: mspgcc-users@lists.sourceforge.net
Subject: Re: [Mspgcc-users] gdb-loop in Mspdebug
On Mon, N
it is gdb_loop not gdb-loop under vs. dash.
ouch.
took me a while to see it.
On Sun, Nov 3, 2013 at 7:21 PM, Andrew McLaren wrote:
> I'm running Mspdebug outboard of Eclipse. In the old gdbproxy, once I set
> this listening on its input port, it remained active until it was
> explicitly
On Mon, Nov 04, 2013 at 04:21:56PM +1300, Andrew McLaren wrote:
> I'm running Mspdebug outboard of Eclipse. In the old gdbproxy, once I set
> this listening on its input port, it remained active until it was explicitly
> stopped. With Mspdebug, if the debug session is stopped in Eclipse, Mspdebug
>
I'm running Mspdebug outboard of Eclipse. In the old gdbproxy, once I set
this listening on its input port, it remained active until it was explicitly
stopped. With Mspdebug, if the debug session is stopped in Eclipse, Mspdebug
returns to its [mspdebug] prompt, and the "gdb [port]" command needs to
