Re: [Xen-devel] [Xen-users] 1000 Domains: Not able to access Domu via xm console from Dom0

[Wei Liu <Wei.Liu2@xxxxxxxxxx>]

On Fri, 2012-12-14 at 13:06 +0000, Paul Harvey wrote:
> SO
> 
> #with 341 domains
> ./lsevntchn 0 | wc -l
> 724
> 
> Attaching gdb to xenconsoled, 
> 
> Program received signal SIGABRT, Aborted.
> 0x00007fe588ca8425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
> (gdb) bt
> #0  0x00007fe588ca8425 in raise ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #1  0x00007fe588cabb8b in abort ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #2  0x00007fe588ce639e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
> #3  0x00007fe588d7c807 in __fortify_fail ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #4  0x00007fe588d7b700 in __chk_fail ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #5  0x00007fe588d7c7be in __fdelt_warn ()
> from /lib/x86_64-linux-gnu/libc.so.6
> #6  0x0000000000403ca8 in handle_io () at daemon/io.c:1059
> #7  0x00000000004021c5 in main (argc=2, argv=0x7fff58691d48) at
> daemon/main.c:166
> 

libc raises exception when it detects memory violation.

You can probably try to use valgrind to identify memory leak in
xenconsoled.


Wei.


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