On 8/29/2012 4:44 AM, andy pugh wrote:
> On 29 August 2012 05:07, Kent A. Reed <[email protected]> wrote:
>
>> and it's 353 bugs.
> And this one is mine:
> "Memory - illegal accesses    /hal/components/bldc.comp"
>
> But I am not sure how to find which program line(s) it doesn't like.
>

Andy.

I looked on the Coverity Integrity Manager site and discovered two things.

First, the .csv file that they let me download has subtle differences 
from the table presented on the website. At the moment, I see a few file 
names are different (but see their explanation of the bug below, which 
gives a clue why).

-In the .csv file, "your" bug (they call them defects by the way; I'm a 
throw-back to the 1960s when operators hung a can of Raid bugspray next 
to the user console as an insider joke) is identified as you see.

-On the website, the file name is identified as 
"/usr/src/linux-headers-2.6.32-122-rtai/hal/components/bldc.comp".

Second, when I clicked through  to the source, I get the reply "/* This 
file does not exist. Perhaps it was a temporary generated file, or only 
appearing in a # line*/"

At the moment, I have access only to a virtual host on which I built a 
LinuxCNC simulator from sources. On this machine, 
"/usr/src/linux-headers-2.6.32-122-rtai/hal/" doesn't exist but of 
course the build is complete.

Using these tools is like dropping acid; you're in for an interesting trip.

Regards,
Kent

PS - on this same virtual host, I see a link 
/usr/src/linux-headers-2.6.32-122-rtai/sources -> 
/home/moses/Projects/emc2/ubuntu-lucid

Does anyone know where that came from and  why?

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to