They do use GDB (as we do). Just remember our plans to use VS in the end via
a custom debugging service. What I am saying, and what Dennis was probably
saying, was that IL kernel debugging should be on common grounds (that is,
once we start debugging in an IDE).
User-space? Each man for himself I think. A common symbol library format
would help though.
On 28/01/2008, Matthijs ter Woord <[EMAIL PROTECTED]> wrote:
>
> Are we talking about Kernel debugging here or user-space debugging?
>
> If it's kernel debugging, why not (try to) use gdb?
>
>
>
>
> On Jan 28, 2008 8:18 AM, Jonathan Dickinson <[EMAIL PROTECTED]>
> wrote:
>
> >
> >
> > On 28/01/2008, Chad Z. Hower aka Kudzu <[EMAIL PROTECTED]> wrote:
> > >
> > > > . Common kernel debug driver/standard
> > >
> > > I doubt we will be able to consolidate on a driver model. I don't
> > > think
> > > either wants to be restricted by the other.
> >
> >
> > It's a bit hard/fast but I don't know the status of debugging .net in
> > linux??? Which means the linux side of things are not really going to run
> > away from writing a debugging system. Can anyone elaborate please?
> >
> > As far as the debugging standard goes a protocol (which I started
> > hashing out in my original post) could be common ground. That way,
> > hopefully, the SharpOS team could piggy-back off of Cosmos VS debugging. At
> > such a time where we have a PDB -> DBG (or such) converter Cosmos could
> > piggy-back off of what the linux team did (that is also when Mono supports
> > .Net 3.x).
> >
> > Debug over ethernet would be much more verstatile than serial, but
> > serial is do-able. What we need to do is to flesh out a debug protocol
> > (maybe based on the windows/linux kernel debug stuff) that we both
> > could/should/must use.
> >
> > Driver was really the wrong word to use, just how that driver
> > communicates with the outside world should be a standard between the two
> > projects.
> >
> > > o Ethernet is fast, easier to use in the end (think VMWare/VPC/other
> > > > that don't play with us nicely) So to hash out something that the
> > > > kernel driver would need:
> > >
> > > Im working on Ethernet support already.
> > >
> > >
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Microsoft
> > > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > _______________________________________________
> > > SharpOS-Developers mailing list
> > > SharpOS-Developers@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/sharpos-developers
> > >
> >
> >
> >
> > --
> > Jonathan
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > SharpOS-Developers mailing list
> > SharpOS-Developers@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/sharpos-developers
> >
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> SharpOS-Developers mailing list
> SharpOS-Developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sharpos-developers
>
>
--
Jonathan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
