[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] wsg_separation Issue
From: |
Bywater, Rick (SA-1) |
Subject: |
Re: [gpsd-dev] wsg_separation Issue |
Date: |
Mon, 7 May 2012 10:15:05 -0400 |
Eric,
Here is a log of a Coverity run on the head as of this morning. The gpsd.log
contains the output from the cov-build while gpsd.log2 contains the
cov-analyze output. I was going to attach the full c/ directory that Coverity
generates so you could see the issues, but the tgz file was over 12 MB and I
was afraid that would be rejected by the mailing list. If you would like that
output and the list server is ok with a 12 MB file, let me know and I will
post it. If the list server will reject that size of an upload, let me know
where you would like the results posted and I will get them uploaded.
Thanks,
Rick
-----Original Message-----
From: Eric S. Raymond [mailto:address@hidden
Sent: Sunday, May 06, 2012 11:51 PM
To: Bywater, Rick (SA-1)
Cc: address@hidden
Subject: Re: [gpsd-dev] wsg_separation Issue
Bywater, Rick (SA-1) <address@hidden>:
> I was running Coverity on gpsd-2.39 and it complained about an
> array-bounds issue in geoid.c in the function wsg84_separation.
We've incorporated a fix patch to the repo head version.
Please run Coverity on repo head and post the results here. I'd *love* to see
a current Coverity defect list. We're on their list of projects allowed to
self-scan from their website, but they have never gotten that machinery
together enough that we can actually do it from here.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
NOTICE: This e-mail transmission (and/or the attachments accompanying it) may
contain confidential or proprietary information belonging to DRS Technologies
or the sender. The information is only for the use of the intended recipient.
If you are not the intended recipient you are hereby notified that any
disclosure, copying, distribution or the taking of any action in reliance on
the contents of this information is strictly prohibited. Any unauthorized
interception of this transmission is illegal under the law. If you have
received this transmission in error, please promptly notify the sender by reply
e-mail, and then destroy all copies of the transmission.
"This (document/presentation) may contain technical data as defined in the
International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. Export of this
material is restricted by the Arms Export Control Act (22 U.S.C. 2751 et seq.)
and may not be exported to foreign persons without prior written approval from
the U.S. Department of State."
gpsd.log
Description: Binary data
gpsd.log2
Description: Binary data
smime.p7s
Description: S/MIME cryptographic signature
Re: [gpsd-dev] wsg_separation Issue, Eric S. Raymond, 2012/05/06
- Re: [gpsd-dev] wsg_separation Issue,
Bywater, Rick (SA-1) <=
- Re: [gpsd-dev] wsg_separation Issue, Eric S. Raymond, 2012/05/08
- Re: [gpsd-dev] wsg_separation Issue, Bywater, Rick (SA-1), 2012/05/09
- Re: [gpsd-dev] wsg_separation Issue, Dave Hart, 2012/05/09
- Re: [gpsd-dev] wsg_separation Issue, Eric S. Raymond, 2012/05/10
- Re: [gpsd-dev] wsg_separation Issue, Bywater, Rick (SA-1), 2012/05/10
- Re: [gpsd-dev] wsg_separation Issue, Eric S. Raymond, 2012/05/09