On Sat, 28 Nov 2009, Kyle McMartin wrote: > > From: Helge Deller <deller@xxxxxx> > > kernel unwinding is broken with gcc >= 4.x. Part of the problem is, that > binutils seems sensible where the unwind information is stored. The commentary doesn't seem to make much sense to me. Do you mean "sensitive" rather than "sensible"? And is it an actual binutils bug, or what? Also, are the PARISC people 100% sure that you really want unwinding in the first place? We got rid of it as being terminally broken on x86, because tools and asm always got it wrong, and special things like irq frames etc continually broke it in the most annoying ways possible (ie WARN_ON() statements became fatal oopses due to unwind errors etc). Having a tentative and unreliable stack trace is generally better than a totally broken one. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
