![]() | ||||||||||
Messages in this thread |
> That's not for me to judge, but I believe it has always been like that. No, normally /proc/kallsyms looks similar to System.tap. Where are all these DW.* symbols coming from? They didn't use to be there and don't make any sense because they don't have any valid kernel addresses. > I just wanted to understand if you noticed a change in behavior (which > is probably a bug) or if it has always been like that but you just > noticed how ugly it is. I noticed a change in behavior. > Maybe you also have some debug or markers configuration or something > that is generating extra symbols to a special section that is just > making the problem look worse now. Nothing particular. I uploaded the config at http://halobates.de/basil-config > Anyway, I can change the way kallsyms works, but that has to be done > with some care because there are some userspace tools that read > /proc/kallsyms and we don't want to break those. A proper testing period > through -mm should take care of that, though. It's the other way round -- kallsyms changed and that change will likely break programs. -Andi -- 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/ | |||||||||
| Last update: 2008-05-09 23:19 [W:0.080 / U:0.740 seconds] ©2003-2008 Jasper Spaans | ||||||||||