On 21/05/13 18:20, Massimo Maiurana wrote:
> Christopher Michael, il 21/05/2013 15:37, ha scritto:
>
>> Found the leak, and plugged it ;) It's in git now. Also, ran the whole
>> thing through valgrind myself and there are no more leaks coming from
>> ecore_x_randr that I found. Hopefully this fixes
Christopher Michael, il 21/05/2013 15:37, ha scritto:
> Found the leak, and plugged it ;) It's in git now. Also, ran the whole
> thing through valgrind myself and there are no more leaks coming from
> ecore_x_randr that I found. Hopefully this fixes your problem :)
Thanks, the first login was wit
On 21/05/13 11:43, Massimo Maiurana wrote:
> Chris Michael, il 18/05/2013 22:44, ha scritto:
>
>> Well, engine should not matter in the case of your randr valgrind stuff
>> because the one (render engine) has nothing to do with the other
>> (ecore_x_randr calls) but let me know.
>
> You're righ
On 18/05/13 21:36, Massimo Maiurana wrote:
> Chris Michael, il 18/05/2013 13:40, ha scritto:
>> On 18/05/13 12:15, Massimo Maiurana wrote:
>>> Chris Michael, il 18/05/2013 13:01, ha scritto:
>>>
Hmmm, this must be an older EFL ?? because these line numbers are not
matching up with what I
Chris Michael, il 18/05/2013 13:40, ha scritto:
> On 18/05/13 12:15, Massimo Maiurana wrote:
>> Chris Michael, il 18/05/2013 13:01, ha scritto:
>>
>>> Hmmm, this must be an older EFL ?? because these line numbers are not
>>> matching up with what I have from git...
>> It's a 1 week old git version,
On 18/05/13 12:15, Massimo Maiurana wrote:
> Chris Michael, il 18/05/2013 13:01, ha scritto:
>
>> Hmmm, this must be an older EFL ?? because these line numbers are not
>> matching up with what I have from git...
> It's a 1 week old git version, so those lines could have been shifted by
> other comm
Chris Michael, il 18/05/2013 13:01, ha scritto:
> Hmmm, this must be an older EFL ?? because these line numbers are not
> matching up with what I have from git...
It's a 1 week old git version, so those lines could have been shifted by
other commits.
--
Massimo Maiurana GPG k
On 18/05/13 09:41, Cedric BAIL wrote:
> Hello,
>
> On Thu, May 16, 2013 at 3:08 PM, Massimo Maiurana wrote:
>> Cedric BAIL, il 15/05/2013 02:44, ha scritto:
>>> The backtrace are not useful as it seems to be a memory corruption.
>>> Could you try by running enlightenment_start -valgrind and tell u
Hello,
On Thu, May 16, 2013 at 3:08 PM, Massimo Maiurana wrote:
> Cedric BAIL, il 15/05/2013 02:44, ha scritto:
>> The backtrace are not useful as it seems to be a memory corruption.
>> Could you try by running enlightenment_start -valgrind and tell us if
>> it spot any memory corruption ?
>
> Fo
On Tue, May 14, 2013 at 8:30 PM, Massimo Maiurana wrote:
> The attached crashdump contains two backtraces, one from yesterday
> startup and the other from the today one.
> This is from a saturday night update of my local repo, completely
> rebuilt of course.
> Only the first startup, two days ago,
The attached crashdump contains two backtraces, one from yesterday
startup and the other from the today one.
This is from a saturday night update of my local repo, completely
rebuilt of course.
Only the first startup, two days ago, had no problems, every other
startup produces this segfault and at
11 matches
Mail list logo
