[Pkg-clamav-devel] Uploading 0.98.7+dfsg-4

[Andreas Cadhalpun]

Hi Sebastian,

On 30.11.2015 21:19, Sebastian Andrzej Siewior wrote:
> I cherry-picked the commit [0] which is the one that added the ppc bits
> here. Rebuilt llvm. It is still crashing, but now differently, this is
> the output of `clambc unit_tests/input/inflate.cbc --debug` :
[...]
> |LibClamAV debug: [Bytecode JIT]; emitted ELF32-ppc <in-memory object> of 764 bytes

So at least it could compile the bytecode.

> |LibClamAV debug: bytecode self test running
> |LibClamAV debug: Bytecode 4294967295: executing in JIT mode
> |
> |Program received signal SIGSEGV, Segmentation fault.
> |cli_vm_execute_jit (bcs=bcs at entry=0xbfffdfe0, ctx=0x10000, ctx at entry=0x10066470, func=0x10049020) at bytecode2llvm.cpp:2409
> |2409        if (ctx->bytecode_timeout)
> |(gdb) bt
> |#0  cli_vm_execute_jit (bcs=bcs at entry=0xbfffdfe0, ctx=0x10000, ctx at entry=0x10066470, func=0x10049020) at bytecode2llvm.cpp:2409
> |#1  0x0fece0a8 in cli_bytecode_run (bcs=bcs at entry=0xbfffdfe0, bc=bc at entry=0x100385d0, ctx=ctx at entry=0x10066470) at bytecode.c:1841
> |#2  0x0fecec90 in run_selfcheck (bcs=0xbfffdfe0) at bytecode.c:2451
> |#3  selfcheck (engine=<optimized out>, jit=1) at bytecode.c:2484
> |#4  0x0fecefe4 in cli_bytecode_prepare2 (engine=engine at entry=0x10049d58, bcs=bcs at entry=0xbfffe300, dconfmask=dconfmask at entry=15)
> |    at bytecode.c:2675
> |#5  0x100016a8 in main (argc=<optimized out>, argv=<optimized out>) at bcrun.c:360
> |(gdb) p ctx
> |$1 = (cli_bc_ctx *) 0x10000
> |(gdb) p *ctx
> |Cannot access memory at address 0x10000
> 
> *Now* there is a stack, before that there was just garbage…

However, it looks like the produced bytecode isn't quite correct.
Probably this needs more commits from LLVM 3.8, no idea which ones, though.

> Okay. Unless someone objects, I will prepare the unstable & exp release and
> upload tomorrow with ppc-llvm support.

Agreed.

> And then I would
> - open an import bug against c-icap-modules regarding missing clamav support

OK.

> - rebuild rev-deps

They should be still fine, I guess, but more testing shouldn't hurt.

> - prepare a bug against against release.d.o regarding the transition and
>   post here first :)

Isn't it a bit early for that, as 0.99 hasn't been released?

Best regards,
Andreas