From: "kim.jin" <kim.jin@stromasys.com>
To: "Ian Campbell" <Ian.Campbell@citrix.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Re: Re: [Xen-devel] request of suggestions for mini-OS debugger
Date: Fri, 14 Jan 2011 10:35:31 +0800 [thread overview]
Message-ID: <201101141035276736745@stromasys.com> (raw)
In-Reply-To: 20110113123610.GH5995@const.bordeaux.inria.fr
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
Wooo! It looks we have newer weapon. Can you help me to begin use it?
BTW, I will dig into the gdbsx, maybe also gdbserver. And my at last aim is: make debugging for mini-OS easy and powerfull enough. If anyone of you have interesting, WELCOME!
------------------
Best Regards!
Kim King
2011-01-14
-------------------------------------------------------------
>On Thu, 2011-01-13 at 12:36 +0000, Samuel Thibault wrote:
>> kim.jin, le Thu 13 Jan 2011 20:16:30 +0800, a écrit :
>> > Re: [Xen-devel] request of suggestions for mini-OS debugger
>> > >kim.jin, le Thu 13 Jan 2011 19:04:57 +0800, a écrit :
>> > >> Do you think the mini-OS need debugger? I will try to implement it. I have two methods, first follow KDB, and the other follow KGDB.
>> > >> What's your opinions? And can you please give some suggestions? Waiting for your good ideas!
>> > >
>> > >I used to simply use the gdbserver that was in tools/debugger.
>> > >
>> > >Samuel
>> >
>> > You mean it already work well for mini-OS, right?
>>
>> It used to, yes.
>>
>> > sound nice! But can it support source level debug?
>>
>> Just like usual gdb support.
>>
>> > And how can I test the nice tool? I knew it little, thanks!
>>
>> I can't find it in the xen tree any more, I don't know what happened to
>> it.
>
>It was unloved and constantly broken so it was removed.
>
>gdbsx is the replacement.
>
>Ian.
>
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-01-14 2:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 11:04 request of suggestions for mini-OS debugger kim.jin
2011-01-13 11:45 ` Samuel Thibault
2011-01-13 12:16 ` kim.jin
2011-01-13 12:36 ` Samuel Thibault
2011-01-13 12:38 ` Ian Campbell
2011-01-14 2:35 ` kim.jin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201101141035276736745@stromasys.com \
--to=kim.jin@stromasys.com \
--cc=Ian.Campbell@citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.