On Tue, 2013-03-26 at 22:52 +0100, Philippe Waroquiers wrote:
The best would be to file a bug in bugzilla, for the false negative
caused by code such as:
{
size_t undef;
char *p = malloc (undef);
}
Too late to file a bug in bugzilla :).
An improvement has been
\o/
With kind regards / Med vänliga hälsningar
Jonatan Wallmander
Vovoid Media Technologies AB
On 04/04/2013 11:13 PM, Philippe Waroquiers wrote:
On Tue, 2013-03-26 at 22:52 +0100, Philippe Waroquiers wrote:
The best would be to file a bug in bugzilla, for the false negative
caused by code
Feature-request:
Add backtrace to output for these warnings:
Warning: set address range perms: large range
[0x4c339040, 0x206094130) (undefined)
Explanation:
This was a large allocation which ate up all my memory when debugging
with valgrind making it hard for me to find where it
On Tue, 2013-03-26 at 14:30 +0100, Jonatan Wallmander wrote:
Feature-request:
Add backtrace to output for these warnings:
Warning: set address range perms: large range
[0x4c339040, 0x206094130) (undefined)
Probably not difficult to implement, however, see below ...
