public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001490] C99 snprintf() does not include terminated null in truncated strings
Date: Wed, 08 Aug 2012 16:58:00 -0000	[thread overview]
Message-ID: <20120808165838.54E2C2F78005@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001490-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001490

--- Comment #5 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2012-08-08 17:58:35 BST ---
(In reply to comment #4)
> (In reply to comment #3)
> oops, sorry... Now I see, actually I applied the my own patch from
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001628

[snip]

Thanks. Clear.

> Well, there is more trouble with sprintf....
> 
> There is another bug #20804, about the %e format, that is also still
> not fixed.
> 
> When I tried to understand, why that happens, I found a buffer
> overflow in the statement: printf("%.15f", DBL_MAX);
> 
> There is a buffer in vfnprintf() which is 2 characters too small.

There is another case.  Today I investigated in bug #20804.  The reason
is

686             /* trailing f.p. zeroes */
687             PAD(fpprec, zeroes);
688             ret += fpprec;

It's okay for ("%.18f\n", 3.14e-11)

   0.000000000031400000

But the padding/zeroing will be wrong for %e, %E, when requested prec >
MAXPREC. Well, I ever made a fix :-) But, then I Googled and found this
report

  http://www.cygwin.com/ml/ecos-discuss/2001-05/msg00065.html

Well, it looks like my fix (Suzuki did talk about the same point which I
found in GDB), but my workaround was

        if (prec > MAXFRACT) {
                if ((ch == 'f' && ch == 'F') || (flags&ALT)) {
                        fpprec = prec - MAXFRACT;
                        prec = MAXFRACT;
                }
        } else if (prec == -1)

I was suprised how many projects use the same "printf" sources! But I've
seen no fixes in this place there.  I need more time to look around. 

> Maybe there should be a patch for all of the known issues.  What do
> you think?

No matter.  I think we have to rid all the issues. Thank you for your
reports.

Sergei

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2012-08-08 16:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 13:11 [Bug 1001490] New: " bugzilla-daemon
2012-06-27 18:37 ` [Bug 1001490] " bugzilla-daemon
2012-08-07 10:06 ` bugzilla-daemon
2012-08-07 16:44 ` bugzilla-daemon
2012-08-08  7:31 ` bugzilla-daemon
2012-08-08 16:58 ` bugzilla-daemon [this message]
2012-08-09  7:50 ` bugzilla-daemon
2012-08-09  8:52 ` bugzilla-daemon
2012-08-09 10:00 ` bugzilla-daemon
2012-08-09 10:52 ` bugzilla-daemon
2012-08-09 11:04 ` bugzilla-daemon
2013-02-18 22:00 ` bugzilla-daemon
2013-02-19 10:40 ` bugzilla-daemon
2013-02-19 13:58 ` bugzilla-daemon

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=20120808165838.54E2C2F78005@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).