On 04/03/11 11:35, Philip Martin wrote:
> John Beranek <john_at_redux.org.uk> writes:
>
>> On 03/03/11 23:48, Philip Martin wrote:
>>> John Beranek <john_at_redux.org.uk> writes:
>>>
>>>> Forgot to note, same assertion failure:
>>>>
>>>> START: client-test
>>>> lt-client-test: subversion/libsvn_subr/svn_temp_serializer.c:282:
>>>> svn_temp_deserializer__resolve: Assertion `*ptr > buffer' failed.
>>>
>>> A stack trace please:
>>
>> A small note here that confused me, I reconfigured with
>> --enable-maintainer-mode and did a clean build, and the test failures
>> and assertion went away. I was about to send a message apologising for
>> not doing a clean build, but now I find if I turn off maintainer mode
>> and do a clean build, I still get the failures.
>>
>> Here's a backtrace:
>>
>> #0 0x0000003786c330c5 in raise () from /lib64/libc.so.6
>> #1 0x0000003786c34a76 in abort () from /lib64/libc.so.6
>> #2 0x0000003786c2b905 in __assert_fail () from /lib64/libc.so.6
>> #3 0x00007ffff713dd0b in svn_temp_deserializer__resolve (
>> buffer=<value optimized out>, ptr=<value optimized out>)
>> at subversion/libsvn_subr/svn_temp_serializer.c:282
>
> This looks like an optimised build. Does this bug only happen when
> optimisation is enabled?
Is there a recommended way to get -O0 into the compilation in Subversion
build land?
John.
--
John Beranek To generalise is to be an idiot.
http://redux.org.uk/ -- William Blake
Received on 2011-03-04 12:38:21 CET