[M3commit] CVS Update: cm3
Rodney M. Bates
rodney_bates at lcwb.coop
Tue Sep 14 22:23:47 CEST 2010
Please put it back. I am about to use it myself to debug on an older
computer that is using PM3.
Jay K wrote:
> Let's put it back when we need it, if m3gdb supports such target.
> (e.g. it doesn't support ARM_DARWIN anyway).
> Maybe by then the trees in the backen will be good enough that gdb will suffice.
> I use the recent release as a good easy source of getting older code from.
> (easier than cvsweb, which is also available)
>
> Or if you insist I can put it back immediately.
>
>
> - Jay
>
>
> ----------------------------------------
>> Date: Mon, 13 Sep 2010 16:09:51 -0500
>> From: rodney_bates at lcwb.coop
>> To: m3commit at elegosoft.com
>> Subject: Re: [M3commit] CVS Update: cm3
>>
>> Not sure what you mean here. If you mean m3gdb will only be built
>> on the same machine it runs on, I think that is entirely reasonable.
>>
>> If you mean no cross-debuggers (which run on one machine and debug
>> a different one), we should preserve these. Especially with the
>> proliferation of small embedded devices, etc.
>>
>> Probably not much need to be able to build such a cross debugger
>> until somebody has a specific need, but existing separation between
>> HOST (machine gdb runs on) and TARGET (where the debugee program runs)
>> should be preserved in the code so we don't lose the work that went
>> into it.
>>
>> Jay Krell wrote:
>>> CVSROOT: /usr/cvs
>>> Changes by: jkrell at birch. 10/09/13 11:15:55
>>>
>>> Modified files:
>>> cm3/m3-sys/m3gdb/src/: m3makefile
>>> Removed files:
>>> cm3/m3-sys/m3gdb/src/: platforms.quake
>>>
>>> Log message:
>>> remove cross gdb stuff
>>>
>>>
>
More information about the M3commit
mailing list