Hi Bill,
What you may be seeing is Valgrind not being able to detect the memory
aliasing you're using in that complex loop condition ((i <
test_mpn_poly->limbs) && (result == 1)). If you can re-create this
exact error using a similar snipet of code in a tiny example program,
it would be worth se
Sure, that's precisely what I think the error means. I'm just saying I
have code where I don't see anything like this, but valgrind still
reports the error.
The code is quite complex I'm probably just missing something
somewhere. I mean here is essentially the part which causes the error:
result
On Aug 20, 2007, at 2:07 PM, mabshoff wrote:
>> However, there is one "error" which valgrind reports on my own code
>> from time to time which I have been unable to determine the source
>> of.
>> It says something like "conditional jump depends on uninitialised
>> data". I have stared at code
On Aug 20, 8:10 pm, Bill Hart <[EMAIL PROTECTED]> wrote:
> Getting rid of memory leaks also speeds up code dramatically as I
> found out recently. When new memory is allocated by the kernel, it
> isn't quite ready to be used. As you begin writing to it, pages of
> roughly 4kb at a time initiate
Getting rid of memory leaks also speeds up code dramatically as I
found out recently. When new memory is allocated by the kernel, it
isn't quite ready to be used. As you begin writing to it, pages of
roughly 4kb at a time initiate an interrupt which the kernel has to
deal with, called a minor page
