On Wed, Jul 15, 2015 at 8:43 PM, Richard Hipp wrote:
> On 7/15/15, T?r?k Edwin wrote:
>> On 07/15/2015 08:34 PM, T?r?k Edwin wrote:
>>
>> In fact such detection could be added to fuzzcheck.c too (I didn't know that
>> you can detect presence of address sanitizer at compile time until now):
>
> It
On 07/15/2015 08:34 PM, T?r?k Edwin wrote:
> On 07/15/2015 08:17 PM, Richard Hipp wrote:
>> On 7/15/15, T?r?k Edwin wrote:
>>> This might be just the test runner and not sqlite itself, I'm not sure:
>>>
>>> Time: capi2.test 25 ms
>>>
On 07/15/2015 08:17 PM, Richard Hipp wrote:
> On 7/15/15, T?r?k Edwin wrote:
>> This might be just the test runner and not sqlite itself, I'm not sure:
>>
>> Time: capi2.test 25 ms
>> =
>> ==2330==ERROR: AddressSanitizer: heap-use-aft
On 07/15/2015 06:59 PM, Richard Hipp wrote:
> On 7/15/15, T?r?k Edwin wrote:
>>>
>>> 1) unknown-crash (might be due to some alignment requirements in asan):
>>
>> Build with clang 3.4 shows a heap-use-after-free instead of unknown-crash,
>> and building a normal (just ./configure) executable with
On 15 Jul 2015, at 5:28pm, T?r?k Edwin wrote:
> Thanks, do I still need to turn this on if I run 'PRAGMA integrity_check'?
You don't need to turn it on at all. It's there only to get rid of a warning
from clang and a couple of other things.
Simon.
On 07/15/2015 06:19 PM, Richard Hipp wrote:
> On 7/15/15, T?r?k Edwin wrote:
>> On 07/15/2015 12:05 AM, Richard Hipp wrote:
>>
>> I've run the address and undefined behaviour sanitizer (+ usual hardening
>> and bug finding flags from Debian) from GCC 4.9.2 on Debian Jessie on this
>> fossil checko
On 07/15/2015 05:59 PM, T?r?k Edwin wrote:
> On 07/15/2015 12:05 AM, Richard Hipp wrote:
>> The plan is to release SQLite version 3.8.11 on or about the end of July.
>>
>> The current code is passing all tests that we have run against it.
>> Some soak tests are still running. There are quite a few
On 07/15/2015 12:05 AM, Richard Hipp wrote:
> The plan is to release SQLite version 3.8.11 on or about the end of July.
>
> The current code is passing all tests that we have run against it.
> Some soak tests are still running. There are quite a few
> cross-platform tests (running on PPC, Sparc,
On 7/15/15, T?r?k Edwin wrote:
> On 07/15/2015 08:34 PM, T?r?k Edwin wrote:
>
> In fact such detection could be added to fuzzcheck.c too (I didn't know that
> you can detect presence of address sanitizer at compile time until now):
It's a clever idea. I'm not so sure I want to add this to fuzzch
On 7/15/15, T?r?k Edwin wrote:
>
> I've attached a patch that fixes these warnings from GCC
>
No attachments on this mailing list. Can you send the patch via
direct email to me?
--
D. Richard Hipp
drh at sqlite.org
On 7/15/15, T?r?k Edwin wrote:
> This might be just the test runner and not sqlite itself, I'm not sure:
>
> Time: capi2.test 25 ms
> =
> ==2330==ERROR: AddressSanitizer: heap-use-after-free on address
> 0x6180003b58dc at pc 0x7f5bb48
On 7/15/15, T?r?k Edwin wrote:
>>
>> 1) unknown-crash (might be due to some alignment requirements in asan):
>
> Build with clang 3.4 shows a heap-use-after-free instead of unknown-crash,
> and building a normal (just ./configure) executable with GCC and running
> under valgrind shows an invalid r
On 7/15/15, T?r?k Edwin wrote:
> On 07/15/2015 12:05 AM, Richard Hipp wrote:
>
> I've run the address and undefined behaviour sanitizer (+ usual hardening
> and bug finding flags from Debian) from GCC 4.9.2 on Debian Jessie on this
> fossil checkout: a73d7128fbca8dde5e90bd46ee915e39ae07dd1f 2015-0
ite-users at
mailinglists.sqlite.org>; sqlite-dev<mailto:sqlite-dev at
mailinglists.sqlite.org>
Subject: [sqlite] SQLite version 3.8.11 coming soon...
The plan is to release SQLite version 3.8.11 on or about the end of July.
The current code is passing all tests that we have run aga
The plan is to release SQLite version 3.8.11 on or about the end of July.
The current code is passing all tests that we have run against it.
Some soak tests are still running. There are quite a few
cross-platform tests (running on PPC, Sparc, etc) that have yet to be
started, but which should not
15 matches
Mail list logo
