From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] 4xx warnings on cmd_elf.c
Date: Fri, 31 Oct 2008 16:16:15 +0100 [thread overview]
Message-ID: <200810311616.15825.sr@denx.de> (raw)
In-Reply-To: <85126F26-4A40-427B-9959-C20925973994@kernel.crashing.org>
On Friday 31 October 2008, Kumar Gala wrote:
> So when I build a 4xx config I see:
>
> cmd_elf.c: In function 'do_bootvx':
> cmd_elf.c:173: warning: array subscript is below array bounds
> cmd_elf.c:176: warning: array subscript is below array bounds
> cmd_elf.c:181: warning: array subscript is below array bounds
>
> sprintf (build_buf, "ibmEmac(0,0)");
>
> if ((tmp = getenv ("hostname")) != NULL) {
> sprintf (&build_buf[strlen (build_buf - 1)],
> "host:%s ", tmp);
> } else {
> sprintf (&build_buf[strlen (build_buf - 1)],
> ": ");
> }
>
> if ((tmp = getenv ("ipaddr")) != NULL) {
> sprintf (&build_buf[strlen (build_buf - 1)],
> "e=%s ", tmp);
> }
>
>
> these seem suspect.. should this be &build_buf[strlen(build_buf) - 1] ?
I haven't seen those warnings before. Triggered by your newer gcc most likely.
But you seem to be correct. The current code is definitely wrong. And I think
that your version is wrong as well. This should do the "right thing":
&build_buf[strlen(build_buf)]
I have no VxWorks platform to test this though.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-10-31 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 14:30 [U-Boot] 4xx warnings on cmd_elf.c Kumar Gala
2008-10-31 15:16 ` Stefan Roese [this message]
2008-11-01 10:30 ` Niklaus Giger
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=200810311616.15825.sr@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.