mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel printk format string compression: C syntax problem
Date: 06 Jun 2003 11:01:36 -0700	[thread overview]
Message-ID: <1054922496.29652.12.camel@serpentine.internal.keyresearch.com> (raw)
In-Reply-To: <3EE0CF07.2070908@techsource.com>

On Fri, 2003-06-06 at 10:27, Timothy Miller wrote:

> printk( "EIP\200\3164x:[<\3168lx>] CPU\200%d\n" ,0xffff & 
> regs->xcs,regs->eip, (current_thread_info()->cpu));
> 
> GCC 3.0.4 makes the following complaint:
> 
> arch/i386/kernel/process.c:173: warning: too many arguments for format
> 
> What I believe is happening is that where I have the escape code "\316" 
> concatenated with the literal "8", the compiler is seeing it as "\3168" 
> and doesn't want to take it.

No.  Look at the __attribute__ on printk in include/linux/kernel.h.  GCC
believes that printk takes a printf-style format string as its first
argument, but you've mangled the string so that the number of format
specifiers doesn't match the number of arguments.

	<b


  reply	other threads:[~2003-06-06 17:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 17:27 Timothy Miller
2003-06-06 18:01 ` Bryan O'Sullivan [this message]
2003-06-06 18:50   ` Timothy Miller
     [not found] ` <Pine.LNX.4.53.0306061330520.7633@chaos>
2003-06-06 18:49   ` Timothy Miller
2003-06-06 19:16     ` Richard B. Johnson
2003-06-06 19:31       ` Timothy Miller

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=1054922496.29652.12.camel@serpentine.internal.keyresearch.com \
    --to=bos@serpentine.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.com \
    /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

all inboxes | Powered by JetHome®