From: Jesper Juhl <jesper.juhl@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc2-git7 build error with CONFIG_STACK_UNWIND enabled
Date: Sat, 29 Jul 2006 16:37:10 +0200 [thread overview]
Message-ID: <200607291637.10282.jesper.juhl@gmail.com> (raw)
In-Reply-To: <20060729142648.GH6843@martell.zuzino.mipt.ru>
On Saturday 29 July 2006 16:26, Alexey Dobriyan wrote:
> On Sat, Jul 29, 2006 at 03:41:46PM +0200, Jesper Juhl wrote:
> > With 2.6.18-rc2-git7 I get the following build error if I have
> > CONFIG_STACK_UNWIND enabled :
> >
> > CC arch/i386/kernel/traps.o
> > arch/i386/kernel/traps.c: In function `show_trace_log_lvl':
> > arch/i386/kernel/traps.c:193: error: invalid type argument of `->'
> > arch/i386/kernel/traps.c:196: error: invalid type argument of `->'
> > arch/i386/kernel/traps.c:197: error: invalid type argument of `->'
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
>
> --- a/arch/i386/kernel/traps.c
> +++ b/arch/i386/kernel/traps.c
> @@ -190,11 +190,11 @@ static void show_trace_log_lvl(struct ta
> if (unw_ret > 0 && !arch_unw_user_mode(&info)) {
> #ifdef CONFIG_STACK_UNWIND
> print_symbol("DWARF2 unwinder stuck at %s\n",
> - UNW_PC(info.regs));
> + UNW_PC(&info));
> if (call_trace == 1) {
> printk("Leftover inexact backtrace:\n");
> - if (UNW_SP(info.regs))
> - stack = (void *)UNW_SP(info.regs);
> + if (UNW_SP(&info))
> + stack = (void *)UNW_SP(&info);
> } else if (call_trace > 1)
> return;
> else
>
>
I can confirm that this fixes the build error.
Thanks Alexey.
/ Jesper Juhl <jesper.juhl@gmail.com> /
prev parent reply other threads:[~2006-07-29 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 13:41 Jesper Juhl
2006-07-29 14:26 ` Alexey Dobriyan
2006-07-29 14:37 ` Jesper Juhl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200607291637.10282.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome