We are thinking about supporting Visual Studio debug. So we need a few
requirements:

   - Common kernel debug driver/standard
   - Windows users: Needs a PDB 2 open debug symbol format program (they
   can run the tool for linux users)
   - Windows users: Visual Studio
   - Linux users: Mono devel + Plugin? Or some hex junkie to go and
   dissasemble PDB.
   - Reach resolution on how debug should be done:
      - Serial is easy, but as said, slow
      - 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:

   - Out (streaming): current location of code pointer in memory
   - Out (request): data at specific point in memory
   - Out (request): stack trace
   - In: break execution (how the hell are we going to do this?)
   - In: continue execution
   - In: continue execution(long nextInstruction)
   - Out (request): get loc of next instruction
   - Anything else?


On 27/01/2008, William Lahti <[EMAIL PROTECTED]> wrote:

> On Jan 26, 2008 5:16 PM, Chad Z. Hower aka Kudzu <[EMAIL PROTECTED]> wrote:
> > > Can Cosmos and #OS conbine forces for testing?
> >
> > I think that might be a great start. Our toolsets are quite different
> > though, but wherever we have compatibilities and so long as there is
> > reciprocity, I think we should investigate such cooperation.
>
> I'm glad to hear such an open minded response on this topic. I think
> we can work out a way to coordinate our efforts where they overlap, at
> *least* outside of the two kernels. We both have our directions and
> they will continue but that doesn't mean we can't work together where
> we would ultimately write the same code. I elaborated verbosely in the
> off-topic thread, while this one was happening. And as for the
> toolsets who knows how much we can unify there, because we have a
> number of people using Linux here and that shuts them into Windows
> development until the new Mono comes out with support for the new
> features. That's not even delving into the issue of using FOSS in the
> toolset. But it's worth a look.
>
> --
> fury
>
> long name: William Lahti
> handle :: fury
> freenode :: xfury
> blog :: http://xfurious.blogspot.com/
>
> -------------------------------------------------------------------------
> 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
> [email protected]
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/sharpos-developers

Reply via email to