[lkml]   [2001]   [Jul]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] show_trace() module_end = 0?

On Thu, 12 Jul 2001, Hugh Dickins wrote:
> show_trace() contains an erroneous line, introduced in 2.4.6-pre4,
> which disables trace on module text: appears to be from temporary
> testing, since code and comments for tracing module text remain.

It as actually disabled on purpose.

It's there because without it the backtrace is sometimes so full of crud
that it is almost impossible to read.

I chose to disable the module back-trace, because what we should _really_
do is to walk the vmalloc space and verify whether it's a valid address or
not. But as I don't use modules myself, I didn't have much incentive to do
so, or to test that it worked.

The simple "disable module backtraces" approach at least makes the normal
backtraces possible to read sanely (well, you still have the issue that
gcc often ends up leaving tons of empty stackslots around and those can
contain stale information, but that can't be fixed as easily).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:57    [W:0.040 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site