mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Andi Kleen <ak@suse.de>
Cc: jbeulich@novell.com, mingo@elte.hu, linux-kernel@vger.kernel.org,
	discuss@x86-64.org
Subject: Re: [PATCH 6/6] reliable stack trace support (i386 entry.S annotations)
Date: Fri, 26 May 2006 08:43:27 -0700	[thread overview]
Message-ID: <20060526084327.433e2be0.akpm@osdl.org> (raw)
In-Reply-To: <200605260918.52484.ak@suse.de>

Andi Kleen <ak@suse.de> wrote:
>
> You probably need newer binutils.

Don't think so.

With this:

diff -puN arch/i386/kernel/entry.S~a arch/i386/kernel/entry.S
--- devel/arch/i386/kernel/entry.S~a	2006-05-26 08:32:04.000000000 -0700
+++ devel-akpm/arch/i386/kernel/entry.S	2006-05-26 08:36:50.000000000 -0700
@@ -733,6 +733,7 @@ nmi_debug_stack_check:
 
 nmi_16bit_stack:
 	/* create the pointer to lss back */
+	CFI_STARTPROC simple
 	pushl %ss
 	pushl %esp
 	movzwl %sp, %esp

That great stream of assembler errors comes down to:

arch/i386/kernel/entry.S: Assembler messages:
arch/i386/kernel/entry.S:858: Error: open CFI at the end of file; missing .cfi_endproc directive
make[1]: *** [arch/i386/kernel/entry.o] Error 1

So there seems to be a missing startproc in there.

With this:

--- devel/arch/i386/kernel/entry.S~a	2006-05-26 08:32:04.000000000 -0700
+++ devel-akpm/arch/i386/kernel/entry.S	2006-05-26 08:38:43.000000000 -0700
@@ -733,6 +733,7 @@ nmi_debug_stack_check:
 
 nmi_16bit_stack:
 	/* create the pointer to lss back */
+	CFI_STARTPROC simple
 	pushl %ss
 	pushl %esp
 	movzwl %sp, %esp
@@ -850,6 +851,8 @@ ENTRY(arch_unwind_init_running)
 ENDPROC(arch_unwind_init_running)
 #endif
 
+	CFI_ENDPROC
+
 .section .rodata,"a"
 #include "syscall_table.S"
 

I get

arch/i386/kernel/entry.S: Assembler messages:
arch/i386/kernel/entry.S:860: Error: invalid sections for operation on `L0' and `L0'

Which is a bit mysterious.

Still, I expect that with a bit of fiddling this patch can be made to work
with older binutils.  I also suspect there's actually something wrong with
it.


  reply	other threads:[~2006-05-26 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22 13:19 Jan Beulich
2006-05-25  5:23 ` Andrew Morton
2006-05-25  5:41   ` Andrew Morton
2006-05-26  7:00     ` Jan Beulich
2006-05-26  7:18   ` Andi Kleen
2006-05-26 15:43     ` Andrew Morton [this message]
2006-05-26 16:05       ` Andrew Morton
2006-05-26  7:26   ` Jan Beulich
2006-05-26 15:28     ` Andrew Morton

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=20060526084327.433e2be0.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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