On 14.03.2012 08:28, Stian Skjelstad wrote: >> Am 13.03.2012 23:38, schrieb Boaz Harrosh: >>> Since a while now my UMLs are constantly crashing in >>> __module_text_address >>> >>> which makes no sense because if I do gdb> list >>> *(__module_text_address+0xd) >>> I get:t >>> >>> 0x6005614e is in __module_text_address >>> (/media/usr0/export/dev/bharrosh/git/pub/linux-open-osd/kernel/module.c:3469). >>> 3464 * module doesn't get freed during this. >>> 3465 */ >>> 3466 struct module *__module_text_address(unsigned long addr) >>> 3467 { >>> 3468 struct module *mod = __module_address(addr); >>> 3469 if (mod) { >>> 3470 /* Make sure it's within the text section. */ >>> 3471 if (!within(addr, mod->module_init, >>> mod->init_text_size) >>> 3472&& !within(addr, mod->module_core, mod->core_text_size)) >>> 3473 mod = NULL; > > source listing vs where it crashes can be off aslong as you use CFLAGS > with -On where n is greater than 0. So the first thing you can test is to > compile UML with CFLAGS="-g -O0". It might be that it doesn't crash > anymore then, if so, you can try to play with different gcc optimization > flags in order to find out what triggers it.
Building the kernel with -O0 is also dangerous. It relies on the fact that some functions need to be inlined in any case. Thanks, //richard ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel