[Xen-users] How to investigate xl double free or corruption?

[Charles <c@xxxxxxxxxxxxxxxxxxxx>]

Hello xen-users :-)

How to investigate xl double free or corruption?

After rebooting a Debian 7 server with Xen 4.1 tools, one DomU had not 
autostarted.
Tried to start it manually:

root@<redacted>:/etc/xen# xl create <redacted>.cfg
Parsing config file <redacted>.cfg
*** glibc detected *** /usr/lib/xen-4.1/bin/xl: double free or 
corruption (!prev): 0x0000000001649010 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x75bb6)[0x7f2b30ee4bb6]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f2b30ee995c]
/lib/x86_64-linux-gnu/libc.so.6(fclose+0x14d)[0x7f2b30ed5afd]
/usr/lib/xen-4.1/bin/../lib/libxenlight.so(libxl_userdata_store+0x113)[0x7f2b3183f9a3]
/usr/lib/xen-4.1/bin/xl[0x409d37]
/usr/lib/xen-4.1/bin/xl[0x40d56c]
/usr/lib/xen-4.1/bin/xl[0x40599d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f2b30e8dead]
/usr/lib/xen-4.1/bin/xl[0x405b71]
======= Memory map: ========
...

The full trace and the .cfg file are at http://pastebin.com/QGXGPcY1

I do not suspect xl itself or the libraries it uses because it 
(auto)started eight DomUs.
Equally I do not suspect the .cfg file because it:
* has not been changed since Feb 2016
* looks normal
* was used by manual xl create in Dec 2016
* has no features which some or all the other .cfg files do not have

How to investigate this unwanted behaviour?

Best

Charles

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
https://lists.xen.org/xen-users