[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#979609: swt4-gtk segfaults on ppc64el

Hi there,

I tried to bisect between 4.17.0 and 4.18.0 (4.19.0
didn't work either) and found the first offending commit
64ceb09e3297259b58a78b5d6486b1724070a4c9 that makes tracecompass fail
and playing with -DNO_gtk_1check_1button_1set_1inconsistent makes it
work. Soon after f2006cbb02568177a6bfaf074f4e787b3dafdc75 : same kind of
changes and same kind of trick seemed to help.
All those implying GTK port changes and JNI. Also I saw tons of cc
warnings of implicit casts in os.c which is generated by JNIGenerator ..

All in all, I tried with latest git tree as it has other GTK/JNI
improvements and as of v4944r22, it built cleanly and worked well with
tracecompass, syndie and steganosuite.

Maybe not the best answer, but I think it can help going forward.


On Mon, 22 Feb 2021 11:15:29 +0200, Adrian Bunk <bunk@debian.org> wrote:
> On Tue, Jan 12, 2021 at 07:06:36PM +0000, Sudip Mukherjee wrote:
> > I had been testing little more and I can see the same problem with
> > other packages (syndie and stegosuite) which are using
> > libswt-cairo-gtk-4-jni.
> > So, all the three packages using libswt-cairo-gtk-4-jni triggers the
> > segfault in ppc64el.
> Adding debian-powerpc so that a porter can check.
> > Regards
> > Sudip
> cu
> Adrian

Attachment: signature.asc
Description: PGP signature

Reply to: