Hi
I have targeted the issue during release of gsequencer-0.8.7.
I think we should close this bug.
Bests,
Joël
On Mon, May 22, 2017 at 12:19 AM, Joël Krähemann wrote:
> Hi
>
> Just figured out that are mainly issues related
> to memory leakes within the test that can be
> safely ignored.
>
> N
Hi
Just figured out that are mainly issues related
to memory leakes within the test that can be
safely ignored.
Note I have fixed additional issues with this
test:
http://git.savannah.nongnu.org/cgit/gsequencer.git/commit/?h=0.8.x&id=78e7b1877add068e59b18b13e2e3b4e245e0b3d3
On Sun, May 21, 201
Hi
Just recognized every _ unit test fails.
So I'm busy for a while.
Cheers,
Joël
On Sun, May 21, 2017 at 11:15 PM, Joël Krähemann wrote:
> Hi
>
> the stack-trace above should be fixed commit:
>
> http://git.savannah.nongnu.org/cgit/gsequencer.git/commit/?h=0.8.x&id=d6a5a226fa01525bbcce3824dfb
Hi
the stack-trace above should be fixed commit:
http://git.savannah.nongnu.org/cgit/gsequencer.git/commit/?h=0.8.x&id=d6a5a226fa01525bbcce3824dfb5f7e82767eb62
Since I didn't test with address sanitizer this wasn't recognized.
I just do run it now. Might be there other issues.
Bests,
Joël
On
Source: gsequencer
Version: 0.8.0-1
Severity: important
Hi,
While looking at #861645 I noticed that the gsequencer testsuite
crashes on x86 with a heap buffer overflow when AddressSanitizer
(-fsanitize=address) is enabled.
FAIL: ags_midi_buffer_util_test
===
5 matches
Mail list logo
