Problem with kdb kernel debugger patch against 2.2.19

byonic@gmx.net
Thu, 9 May 2002 17:09:35 +0200


Hello linux-kernel@vger.kernel.org,

I patched my 2.2.19 kernel with the SGI kdb patch to have the
ability of kernel debugging and especially debugging of the kernel
modules I write.
I had to install libbfd and the kernel seems just to compile perfectly.
Lateron I get the following error :

/usr/src/linux # make bzImage

[...]

make[2]: Entering directory `/usr/src/kernel-source-2.2.19/lib'
make[2]: Nothing to be done for `all_targets'.
make[2]: Leaving directory `/usr/src/kernel-source-2.2.19/lib'
make[1]: Leaving directory `/usr/src/kernel-source-2.2.19/lib'
make -C arch/i386/kernel
make[1]: Entering directory `/usr/src/kernel-source-2.2.19/arch/i386/kernel'
cc -D__KERNEL__ -I/usr/src/linux/include -D__ASSEMBLY__ -traditional -c entry.S -o entry.o
/tmp/ccVx3zpC.s: Assembler messages:
/tmp/ccVx3zpC.s:774: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:774: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:805: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:805: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:824: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:824: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:920: Warning: using `%ecx' instead of `%cx' due to `l' suffix
/tmp/ccVx3zpC.s:929: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:930: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:943: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:943: Warning: using `%edx' instead of `%dx' due to `l' suffix
/tmp/ccVx3zpC.s:1024: Fatal error: Symbol machine_check already defined.
make[1]: *** [entry.o] Error 1
make[1]: Leaving directory `/usr/src/kernel-source-2.2.19/arch/i386/kernel'
make: *** [_dir_arch/i386/kernel] Error 2

What does
"/tmp/ccVx3zpC.s:1024: Fatal error: Symbol machine_check already
defined." mean, how can I solve it to get my kernel with kdb ?

Note: I'm still using 2.2.19 because of module development to test
kernel modules for 2.2.x.

Thanks in advance, Markus

-- 
Best regards,
 byonic                          mailto:byonic@gmx.net

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/