Mailing List Archive

Hi,
I have tried the 2008 version only, but could not get through the gdb.

Were you successful with that?
Can you kindly inform please!

--
✉ Regards :: Krishna Pavan ✍

I tried the 2008 version too, and I got following error. Is this error the same as yours?

guest0 - mini-os.elf
guest1 - mini-os.elf
emulator: warning: cannot load emulator configuration at '/root/.android/emulator.cfg'

emulator: broken configuration file doesn't have 'window' element
emulator: warning: opening audio output failed

Waiting gdb connection on port 1234
./run.sh: line 1: 15212 Segmentation fault ./emulator -guest0 0x01c00000 mini-os.elf -guest1 0x02c00000 mini-os.elf -show-kernel -system ./images -shell -qemu -s

--
Best Regards,
Jicheng Shi




On 2012-8-2, at 下午11:05, Krishna Pavan <post4pavan@gmail.com> wrote:

> Hi,
> I have tried the 2008 version only, but could not get through the gdb.
>
> Were you successful with that?
> Can you kindly inform please!
>
> --
> ✉ Regards :: Krishna Pavan ✍
>

No, I got a different error!

BTW, You should install some other package, latest one that is related to
audio.

I got a Segmentation fault error, but not this.



On Mon, Aug 6, 2012 at 2:55 PM, shi roger <rogershijicheng@gmail.com> wrote:

> I tried the 2008 version too, and I got following error. Is this error the
> same as yours?
>
> guest0 - mini-os.elf
> guest1 - mini-os.elf
> emulator: warning: cannot load emulator configuration at
> '/root/.android/emulator.cfg'
>
> emulator: broken configuration file doesn't have 'window' element
> emulator: warning: opening audio output failed
>
> Waiting gdb connection on port 1234
> ./run.sh: line 1: 15212 Segmentation fault ./emulator -guest0
> 0x01c00000 mini-os.elf -guest1 0x02c00000 mini-os.elf -show-kernel -system
> ./images -shell -qemu -s
>
> --
> Best Regards,
> Jicheng Shi
>
>
>
>
> On 2012-8-2, at 下午11:05, Krishna Pavan <post4pavan@gmail.com> wrote:
>
> Hi,
> I have tried the 2008 version only, but could not get through the gdb.
>
> Were you successful with that?
> Can you kindly inform please!
>
> --
> ✉ Regards :: Krishna Pavan ✍
>
>
>


--
✉ Regards :: Krishna Pavan ✍

I rebuild the environment in VirtualBox VM, and the segmentation fault point changed to 24912. What additional packages have you installed?

--
Best Regards,
Jicheng Shi




On 2012-8-6, at 下午10:48, Krishna Pavan <post4pavan@gmail.com> wrote:

> No, I got a different error!
>
> BTW, You should install some other package, latest one that is related to audio.
>
> I got a Segmentation fault error, but not this.
>
>
>
> On Mon, Aug 6, 2012 at 2:55 PM, shi roger <rogershijicheng@gmail.com> wrote:
> I tried the 2008 version too, and I got following error. Is this error the same as yours?
>
> guest0 - mini-os.elf
> guest1 - mini-os.elf
> emulator: warning: cannot load emulator configuration at '/root/.android/emulator.cfg'
>
> emulator: broken configuration file doesn't have 'window' element
> emulator: warning: opening audio output failed
>
> Waiting gdb connection on port 1234
> ./run.sh: line 1: 15212 Segmentation fault ./emulator -guest0 0x01c00000 mini-os.elf -guest1 0x02c00000 mini-os.elf -show-kernel -system ./images -shell -qemu -s
>
> --
> Best Regards,
> Jicheng Shi
>
>
>
>
> On 2012-8-2, at 下午11:05, Krishna Pavan <post4pavan@gmail.com> wrote:
>
>> Hi,
>> I have tried the 2008 version only, but could not get through the gdb.
>>
>> Were you successful with that?
>> Can you kindly inform please!
>>
>> --
>> ✉ Regards :: Krishna Pavan ✍
>>
>
>
>
>
> --
> ✉ Regards :: Krishna Pavan ✍
>

Generally Segmentation Fault error does not occur in 32-bit systems.

I have used a 64-bit one, when I worked on it recently.

What is the error? you are getting.

I have gone with that upto using gdb.

I switch to 32-bit system and pass the compilation after applied a patch from http://code.google.com/p/android/issues/detail?id=838. Though the system's running, I have no idea how to open dom0 console. As the User Guide says "open debug console", I guess it means to attach gdb to remote target. Besides gdb, is there any other method to connect to it? My console output is shown bellow, is that right?

[XEN] Using scheduler: Borrowed Virtual Time (bvt)
[XEN] *** LOADING DOMAIN : 0 ***
[XEN] Physical Memory Arrangement: 00200000->02000000
[XEN] VIRTUAL MEMORY ARRANGEMENT:
[XEN] Loaded kernel: c0008000->c00249f4
[XEN] Init. ramdisk: c0025000->c0025000
[XEN] Phys-Mach map: c0025000->c002c800
[XEN] Start info: c002d000->c002e000
[XEN] Page tables: c0030000->c0046000
[XEN] Boot stack: c0046000->c0047000
[XEN] TOTAL: c0000000->c1e00000
[XEN] ENTRY ADDRESS: c0008000
[XEN] [TODO] dma channel access permission, in construct_dom0()
[XEN] [dom0] Bootstrapping .....
[dom0] Xen Minimal OS!
[dom0] Magic : xen-3.0-arm_32
[dom0] Total Pages allocated to this domain : 7680
[dom0] MACHINE address of shared info struct : 0xed000
[dom0] VIRTUAL address of page directory : 0xc0030000
[dom0] Number of bootstrap p.t. frames : 22
[dom0] VIRTUAL address of page-frame list : 0xc0025000
[dom0] VIRTUAL address of pre-loaded module : 0x0
[dom0] Size (bytes) of pre-loaded modules : 0
[dom0] min mfn(min_page in xen) : 0
[dom0] Command-Linux Address : 0xc002d054
[dom0] Command-Line String :
[dom0] flags : 0x3
[dom0] sizeo fo pte_t = 4
[dom0] Shared info Offset = 0x0
[dom0] Shared Info : 0xc0009000
[dom0] MM: Init
[dom0] MM: Initializing page allocator for memory c0049000(49000)-c1e00000(1e00000)
[dom0] MM: initializing page allocator
[dom0] MM: initializing grant table
[dom0] MM: done
[dom0] Initialising timer interface
[dom0] Initialising scheduler
[dom0] Thread "Idle": pointer: 0xc004a00c, stack: 0xc004c000
[dom0] Thread "3": pointer: 0xc004a034, stack: 0xc004e000
[dom0] Thread "4": pointer: 0xc004a05c, stack: 0xc0050000
[dom0] Thread "5": pointer: 0xc004a084, stack: 0xc0052000
[dom0] Thread "6": pointer: 0xc004a0ac, stack: 0xc0054000
*** LOADING DOMAIN : 1 ***
[XEN] Physical Memory Arrangement: 02000000->03000000
[XEN] VIRTUAL MEMORY ARRANGEMENT:
[XEN] Loaded kernel: c0008000->c00249f4
[XEN] Init. ramdisk: c0025000->c0025000
[XEN] Phys-Mach map: c0025000->c0029000
[XEN] Store mfn: c0029000->c002a000
[XEN] Console mfn: c002a000->c002b000
[XEN] Start info: c002b000->c002c000
[XEN] Page tables: c002c000->c003b000
[XEN] Boot stack: c003b000->c003c000
[XEN] TOTAL: c0000000->c1000000
[XEN] ENTRY ADDRESS: c0008000
[XEN] store_mfn physical addres 2029000
[XEN] console_mfn physical addres 202a000
[XEN] [TODO] dma channel access permission, in construct_guest_dom()
[XEN] [dom1] Bootstrapping .....
[dom1] Xen Minimal OS!
[dom1] Magic : xen-3.0-arm_32
[dom1] Total Pages allocated to this domain : 4096
[dom1] MACHINE address of shared info struct : 0xe8000
[dom1] VIRTUAL address of page directory : 0xc002c000
[dom1] Number of bootstrap p.t. frames : 15
[dom1] VIRTUAL address of page-frame list : 0xc0025000
[dom1] VIRTUAL address of pre-loaded module : 0x0
[dom1] Size (bytes) of pre-loaded modules : 0
[dom1] min mfn(min_page in xen) : 0
[dom1] Command-Linux Address : 0xc002b054
[dom1] Command-Line String :
[dom1] flags : 0x0
[dom1] sizeo fo pte_t = 4
[dom1] Shared info Offset = 0x1
[dom1] Shared Info : 0xc000a000
[dom1] MM: Init
[dom1] MM: Initializing page allocator for memory c003e000(3e000)-c1000000(1000000)
[dom1] MM: initializing page allocator
[dom1] MM: initializing grant table
[dom1] MM: done
[dom1] Initialising timer interface
[dom1] Initialising scheduler
[dom1] Thread "Idle": pointer: 0xc003f00c, stack: 0xc0040000
[dom1] Thread "3": pointer: 0xc003f034, stack: 0xc0042000
[dom1] Thread "4": pointer: 0xc003f05c, stack: 0xc0044000
[dom1] Thread "5": pointer: 0xc003f084, stack: 0xc0046000
[dom1] Thread "6": pointer: 0xc003f0ac, stack: 0xc0048000
[dom1] 3 Thread
[dom0] 3 Thread
[dom1] 4 Thread
[dom0] 4 Thread
[dom0] 5 Thread
[dom1] 5 Thread
[dom1] 6 Thread
[dom0] 6 Thread
[dom0] After 3 Thread
[dom1] After 3 Thread
[dom1] 3 Thread
[dom0] 3 Thread
[dom1] After 4 Thread
[dom0] After 4 Thread
[dom1] 4 Thread
[dom0] 4 Thread
[dom1] After 5 Thread
[dom0] After 5 Thread
[dom1] 5 Thread
[dom0] 5 Thread
[dom1] After 6 Thread
[dom0] After 6 Thread
[dom1] 6 Thread
[dom0] 6 Thread
[dom1] After 3 Thread
[dom0] After 3 Thread
[dom1] 3 Thread
[dom0] 3 Thread
[dom1] After 4 Thread
[dom0] After 4 Thread
[dom1] 4 Thread
[dom0] 4 Thread
[dom1] After 5 Thread
[dom0] After 5 Thread
[dom1] 5 Thread
[dom0] 5 Thread
[dom1] After 6 Thread
[dom0] After 6 Thread
[dom1] 6 Thread
[dom0] 6 Thread
--
Best Regards,
Jicheng Shi




On 2012-8-10, at 上午12:15, Krishna Pavan <post4pavan@gmail.com> wrote:

> Generally Segmentation Fault error does not occur in 32-bit systems.
>
> I have used a 64-bit one, when I worked on it recently.
>
> What is the error? you are getting.
>
> I have gone with that upto using gdb.

Hi,

So far so good!

Yeah! It's 64-bit systems, that are causing segmentation faults.

Do you have Android Debugger in your PC?
something like adb in your PC?

If you want to use gdb, then you should add it to the script.

It will help you.

Can you please tell me, if, other than applying a patch, did you make any
modifications to the android-on-qemu-2008 package?

Please tell me.

Thanks & Regards :: Krishna Pavan

No other modification is made, and only this patch is applied. The patch adds a flag in Makefile.

--
Best Regards,
Jicheng Shi




On 2012-8-11, at 上午10:57, Krishna Pavan <post4pavan@gmail.com> wrote:

> Hi,
>
> So far so good!
>
> Yeah! It's 64-bit systems, that are causing segmentation faults.
>
> Do you have Android Debugger in your PC?
> something like adb in your PC?
>
> If you want to use gdb, then you should add it to the script.
>
> It will help you.
>
> Can you please tell me, if, other than applying a patch, did you make any modifications to the android-on-qemu-2008 package?
>
> Please tell me.
>
> Thanks & Regards :: Krishna Pavan