On 2015-06-01 17:32-0400 Jim Dishaw wrote:
>>> On May 31, 2015, at 9:32 PM, Alan W. Irwin
>>> wrote:
>>> The remaining warnings are
>>>
>>> /home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function
>>> ‘read_header’:
>>> /home/software/plplot/HEAD/plplot.git/src/plmetafile.c:341:8: wa
> On May 31, 2015, at 10:11 PM, Jim Dishaw wrote:
>
> Yep, I will take a look
>
>
>
>> On May 31, 2015, at 9:32 PM, Alan W. Irwin wrote:
>>
>>> On 2015-05-31 22:06+0100 Phil Rosenberg wrote:
>>>
>>> Hi Alan
>>> You should now find that the plbuf.c warning is gone. I haven't
>>> touched the
Yep, I will take a look
> On May 31, 2015, at 9:32 PM, Alan W. Irwin wrote:
>
>> On 2015-05-31 22:06+0100 Phil Rosenberg wrote:
>>
>> Hi Alan
>> You should now find that the plbuf.c warning is gone. I haven't
>> touched the plmeta files. I will leave these to Jim as I don't know
>> that code
On 2015-05-31 22:06+0100 Phil Rosenberg wrote:
> Hi Alan
> You should now find that the plbuf.c warning is gone. I haven't
> touched the plmeta files. I will leave these to Jim as I don't know
> that code well.
@ Phil: I confirm you fix, and thanks!
@Jim:
The remaining warnings are
/home/softw
Hi Alan
You should now find that the plbuf.c warning is gone. I haven't
touched the plmeta files. I will leave these to Jim as I don't know
that code well.
Phil
On 31 May 2015 at 20:14, Alan W. Irwin wrote:
> On 2015-05-31 18:59+0100 Phil Rosenberg wrote:
>
>> Hi Alan
>> I've worked this out, th
On 2015-05-31 18:59+0100 Phil Rosenberg wrote:
> Hi Alan
> I've worked this out, the line in question is in a function called
> with the possibly uninitialized variable.
> I'm writing the code now to double check everything although the only
> case where we could get an uninitialized variable woul
On 2015-05-31 18:33+0100 Phil Rosenberg wrote:
> Hi Alan
> I'm attacking my to do list. Do you still get these warnings? I just
> looked and the line 1309 no longer makes sense in terms of a reference
> to cmd so I guess the code has changed since then. I don't get any
> unallocated variable warni
Hi Alan
I've worked this out, the line in question is in a function called
with the possibly uninitialized variable.
I'm writing the code now to double check everything although the only
case where we could get an uninitialized variable would be for a
corrupted buffer.
Phil
On 31 May 2015 at 18:
Hi Alan
I'm attacking my to do list. Do you still get these warnings? I just
looked and the line 1309 no longer makes sense in terms of a reference
to cmd so I guess the code has changed since then. I don't get any
unallocated variable warnings for plbuf in VC++ so perhaps someone
else fixed this
To Phil:
gcc is generating these warnings when building libplplot. Would you
please take a look to see whether this is either a real uninitialized issue
that needs to be fixed or a false alarm?
/home/software/plplot/HEAD/plplot.git/src/plmetafile.c: In function
‘read_header’:
/home/software/plp
10 matches
Mail list logo
