How to debug the minios in xen ?

How to debug the minios in xen ?

[马磊]

[-- Attachment #1.1: Type: text/plain, Size: 761 bytes --]

Hi,
    The minios source code is in extra/minios. After compiling, I got a
file called mini-os.gz, then I succeed to start a domainU by setting the
kernerl to be mini-os.gz in config file 'minios.conf' as follow:
# Kernel image file.
kernel = "/home/test/minios.gz"

    The command 'xm list' show:
Name                                        ID   Mem VCPUs      State
Time(s)
Domain-0                                     0  1220     2     r-----
 11527.3
minios-120                                   5   256     1     --p---
1110.5

    I got the gdbserver-xen later and run 'gdbserver-xen
127.0.0.1:9999--attach 5'(5 is the domid). Next, run 'gdb
/path/to/minios/exefile', and
then 'bt' in gdb, but no stack info.
    thanks in advance for your help.

bruce

[-- Attachment #1.2: Type: text/html, Size: 1035 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: How to debug the minios in xen ?

[Daniel Kiper]

On Tue, Mar 13, 2012 at 02:16:26PM +0800, ?????? wrote:
> Hi,
>     The minios source code is in extra/minios. After compiling, I got a
> file called mini-os.gz, then I succeed to start a domainU by setting the
> kernerl to be mini-os.gz in config file 'minios.conf' as follow:
> # Kernel image file.
> kernel = "/home/test/minios.gz"
>
>     The command 'xm list' show:
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0  1220     2     r-----
>  11527.3
> minios-120                                   5   256     1     --p---
> 1110.5
>
>     I got the gdbserver-xen later and run 'gdbserver-xen
> 127.0.0.1:9999--attach 5'(5 is the domid). Next, run 'gdb
> /path/to/minios/exefile', and
> then 'bt' in gdb, but no stack info.
>     thanks in advance for your help.

Hmmm... I think that you forgot to connect to gdbserver-xen.
Run following command from gdb: target remote :9999
and do not forget compile mini-os with symbols.

Daniel

Re: How to debug the minios in xen ?

[马磊]

[-- Attachment #1.1: Type: text/plain, Size: 1398 bytes --]

On Wed, Mar 14, 2012 at 9:27 PM, Daniel Kiper <dkiper@net-space.pl> wrote:

> On Tue, Mar 13, 2012 at 02:16:26PM +0800, ?????? wrote:
> > Hi,
> >     The minios source code is in extra/minios. After compiling, I got a
> > file called mini-os.gz, then I succeed to start a domainU by setting the
> > kernerl to be mini-os.gz in config file 'minios.conf' as follow:
> > # Kernel image file.
> > kernel = "/home/test/minios.gz"
> >
> >     The command 'xm list' show:
> > Name                                        ID   Mem VCPUs      State
> > Time(s)
> > Domain-0                                     0  1220     2     r-----
> >  11527.3
> > minios-120                                   5   256     1     --p---
> > 1110.5
> >
> >     I got the gdbserver-xen later and run 'gdbserver-xen
> > 127.0.0.1:9999--attach 5'(5 is the domid). Next, run 'gdb
> > /path/to/minios/exefile', and
> > then 'bt' in gdb, but no stack info.
> >     thanks in advance for your help.
>
> Hmmm... I think that you forgot to connect to gdbserver-xen.
> Run following command from gdb: target remote :9999
> and do not forget compile mini-os with symbols.
>
> Daniel
>
Thanks，I'll have a try.
I'm not clear about compiling mini-os with symbols, does it make sense that
specifing the /path/to/minios-source in gdb cmd line and the gdb would find
the symbols infomation automatically?

[-- Attachment #1.2: Type: text/html, Size: 2048 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: How to debug the minios in xen ?

[Daniel Kiper]

On Thu, Apr 19, 2012 at 11:53:11PM +0800, ?????? wrote:
> On Wed, Mar 14, 2012 at 9:27 PM, Daniel Kiper <dkiper@net-space.pl> wrote:
>
> > On Tue, Mar 13, 2012 at 02:16:26PM +0800, ?????? wrote:
> > > Hi,
> > >     The minios source code is in extra/minios. After compiling, I got a
> > > file called mini-os.gz, then I succeed to start a domainU by setting the
> > > kernerl to be mini-os.gz in config file 'minios.conf' as follow:
> > > # Kernel image file.
> > > kernel = "/home/test/minios.gz"
> > >
> > >     The command 'xm list' show:
> > > Name                                        ID   Mem VCPUs      State
> > > Time(s)
> > > Domain-0                                     0  1220     2     r-----
> > >  11527.3
> > > minios-120                                   5   256     1     --p---
> > > 1110.5
> > >
> > >     I got the gdbserver-xen later and run 'gdbserver-xen
> > > 127.0.0.1:9999--attach 5'(5 is the domid). Next, run 'gdb
> > > /path/to/minios/exefile', and
> > > then 'bt' in gdb, but no stack info.
> > >     thanks in advance for your help.
> >
> > Hmmm... I think that you forgot to connect to gdbserver-xen.
> > Run following command from gdb: target remote :9999
> > and do not forget compile mini-os with symbols.
> >
> > Daniel
> >
> Thanks???I'll have a try.
> I'm not clear about compiling mini-os with symbols, does it make sense that
> specifing the /path/to/minios-source in gdb cmd line and the gdb would find
> the symbols infomation automatically?

It looks that minios is compiled with debug symbols by default
(I tested it on almost latest Xen Ver. 4.1 tree). It means that
if you pass path to mini-os executable to gdb everything should
work as expected.

Daniel