Displaying 2 results from an estimated 2 matches for "xlu_cfg_readdata".
2010 Aug 03
1
[PATCH] libxl: free values in XLU_ConfigSetting
...e_malloc.c:236)
==21170== by 0x411B22F: strdup (in /lib/i686/cmov/libc-2.7.so)
==21170== by 0x4030085: xlu__cfgl_strdup (libxlu_cfg.c:290)
==21170== by 0x402F3C4: xlu__cfg_yylex (libxlu_cfg_l.l:37)
==21170== by 0x402DD86: xlu__cfg_yyparse (libxlu_cfg_y.c:1338)
==21170== by 0x40308AE: xlu_cfg_readdata (libxlu_cfg.c:85)
==21170== by 0x804DBE4: parse_config_data (xl_cmdimpl.c:591)
==21170== by 0x8056EE4: create_domain (xl_cmdimpl.c:1381)
==21170== by 0x80582AE: main_create (xl_cmdimpl.c:3178)
==21170== by 0x804B54B: main (xl.c:76)
==21170==
==21170== 57 bytes in 2 blocks are definitely...
2012 Aug 14
12
[TESTDAY] xl cpupool-create segfaults if given invalid configuration
...expected IDENT, expecting NEWLINE or '';''
Failed to parse config file: Invalid argument
*** glibc detected *** xl: free(): invalid pointer: 0x0000000001a79a10 ***
Segmentation fault (core dumped)
Looking at the code in xl_cmdimpl.c:main_cpupoolcreate() it calls:
* xlu_cfg_init()
* xlu_cfg_readdata()
if the readdata() fails, it calls xlu_cfg_destroy() before returning.
Other callers to readdata() seem to call exit(1) if readdata() fails.
So is readdata() leavnig the config in an inconsistent state? Or is
config already cleaned up?
-George