|
kgdb's weak symbols vs. gcc 4.1: msg#00031linux.kernel.debugging.kgdb.bugs
Hi, I stumbled over some issue of kgdb in combination with gcc 4.1 since kernel 2.6.16. The background can be found in [1]. It melts down that the default arch-dependent functions in kernel/kgdb.c got compiled in - and immediately optimised out again. The effect is, of course, lethal. As a workaround I added "CFLAGS_kgdb.o += -fno-unit-at-a-time" to kernel/Makefile, but I'm not sure if this is the preferred solution here. Alternatives might be to move all default arch-stubs into a separate object file, thus giving the linker the chance again to handle them, or to use #ifndef KGDB_HAVE_ARCH_xxx constructs. Jan PS: Please CC me on reply. [1] http://gcc.gnu.org/ml/gcc-help/2006-05/msg00202.html
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: 2.6.13 snapshot (by date) still has E22 bug for serial debuging; how do I get locals for scopes other than the outer most block?: 00031, Amit S. Kale |
|---|---|
| Next by Date: | Re: kgdb's weak symbols vs. gcc 4.1: 00031, Tom Rini |
| Previous by Thread: | Re: 2.6.13 snapshot (by date) still has E22 bug for serial debuging; how do I get locals for scopes other than the outer most block?i: 00031, Amit S. Kale |
| Next by Thread: | Re: kgdb's weak symbols vs. gcc 4.1: 00031, Tom Rini |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |