Sometimes developers need to see more object code in an oops report,
e.g. when kernel may be corrupted at runtime.
Add the "code_bytes" option for this.
Signed-off-by: Chuck Ebbert <[EMAIL PROTECTED]>
Documentation/kernel-parameters.txt |5 +
arch/i386/kernel/traps.c| 20
> This was patch inspired by my finding out that code in the running
> kernel might have
> been modified at runtime by some strange bug, and looking at vmlinux
> might not be
> helpful.
Hmm ok, although I still suspect in such a case you'll be better
off with a full kcrash dump.
-Andi
-
To unsub
Andi Kleen wrote:
> On Friday 26 January 2007 00:56, Chuck Ebbert wrote:
>
>
>> Can't think of a way to word the justification, but I've wanted to see more
>> code a few times.
>>
>
> Hmm, not sure I see the point. The Code line is just that you can
> make sense of random mailing list oopse
On Friday 26 January 2007 00:56, Chuck Ebbert wrote:
> Can't think of a way to word the justification, but I've wanted to see more
> code a few times.
Hmm, not sure I see the point. The Code line is just that you can
make sense of random mailing list oopses where you don't
have a vmlinux. But as
Andrew Morton wrote:
> On Wed, 24 Jan 2007 15:22:49 -0500
> Chuck Ebbert <[EMAIL PROTECTED]> wrote:
>
>
>> Sometimes we may need to see more code than the default in an oops,
>> so add an option for that.
>>
>
> spose so, but some more justification would be nice. As would an x86_64
> vers
On Wed, 24 Jan 2007 15:22:49 -0500
Chuck Ebbert <[EMAIL PROTECTED]> wrote:
> Sometimes we may need to see more code than the default in an oops,
> so add an option for that.
spose so, but some more justification would be nice. As would an x86_64
version?
> Signed-off-by: Chuck Ebbert <[EMAIL PR
Sometimes we may need to see more code than the default in an oops,
so add an option for that.
Signed-off-by: Chuck Ebbert <[EMAIL PROTECTED]>
Documentation/kernel-parameters.txt |5 +
arch/i386/kernel/traps.c| 17 +++--
2 files changed, 20 insertions(+), 2 dele
7 matches
Mail list logo
