[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [m4-1.4.11] build feedback
From: |
Bruno Haible |
Subject: |
Re: [m4-1.4.11] build feedback |
Date: |
Sun, 13 Apr 2008 22:26:54 +0200 |
User-agent: |
KMail/1.5.4 |
Tom G. Christensen wrote:
> > Thanks, that's good so far. The interesting stuff is to look
> > - what happens in line vasnprintf.c:2734,
> >
> Single stepping from test-vasprintf-posix:1305 does not seem to stop
> there (closest is 2531)
>
> > - at the result in line vasnprintf.c:4635.
> >
> Single stepping indeed makes a stop at this line, and here result is
> "0.000000 33"
Hmm. That's still not conclusive. I had expected the program to stop at
vasnprintf.c:4635 twice, once with result = "0.000000" and then with
"0.000000 33".
Needs more single-stepping. Where does the "0.000000" string definitely come
from? From the system, I suppose?
You can also try a standalone test program, linked against the system's
sprintf(), like this:
===============================
#include <stdio.h>
int main()
{
char buf[100];
sprintf (buf, "%Lf", -0.0L);
printf ("%s\n", buf);
return 0;
}
===============================
Bruno
- Re: [m4-1.4.11] build feedback, (continued)
- Re: [m4-1.4.11] build feedback, Eric Blake, 2008/04/03
- Re: [m4-1.4.11] build feedback, Bruno Haible, 2008/04/04
- fseek failure output [was: [m4-1.4.11] build feedback], Eric Blake, 2008/04/04
- Re: [m4-1.4.11] build feedback, Bruno Haible, 2008/04/12
- Re: [m4-1.4.11] build feedback, Tom G. Christensen, 2008/04/13
- Re: [m4-1.4.11] build feedback, Bruno Haible, 2008/04/13
- Re: [m4-1.4.11] build feedback, Tom G. Christensen, 2008/04/13
- Re: [m4-1.4.11] build feedback, Bruno Haible, 2008/04/13
- Re: [m4-1.4.11] build feedback, Tom G. Christensen, 2008/04/13
- Re: [m4-1.4.11] build feedback,
Bruno Haible <=
- Re: [m4-1.4.11] build feedback, Tom G. Christensen, 2008/04/14