Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

On Sat, Nov 12, 2016 at 10:00:53PM +0200, Adrian Bunk wrote:
> I do not understand this part.
> 
> -maltivec should only be set for the code that is behind the runtime 
> feature check, so this code is only run on hardware that has AltiVec.

Well a mistake in the configure script is making it set for everything.

After fixing that there is the problem of how to build merge.c in
deinterlace with only -maltivec for the altivec merge function, and not
the rest of the file which is supposed to be the generic C implementation.

I guess like the yuv file that has altivec support, the altivec merge
function needs to be built by itself with -maltivec while the rest of
the file is built without it.

I am trying to figure out how to do that but haven't quite figured it
out yet.  Certainly that is the correct way to fix it.

-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Adrian Bunk]

On Tue, Nov 08, 2016 at 03:29:43PM -0500, Lennart Sorensen wrote:
>...
> -CFLAGS="${CFLAGS} -maltivec"
> +CFLAGS="${CFLAGS} -maltivec -fno-tree-vectorize"
>...
> And I realized the reason it was broken is that when using -maltivec and
> -O4 (which vlc uses), you get -ftree-vectorize automatically enabled
> which means gcc starts to automatically generate vector instructions
> all over the place, which is not desired in this case.  It rather defeats
> the purpose of having a cpu feature check after all.

I do not understand this part.

-maltivec should only be set for the code that is behind the runtime 
feature check, so this code is only run on hardware that has AltiVec.

cu
Adrian

[1] 

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

On Fri, Nov 04, 2016 at 01:33:36PM -0400, Lennart Sorensen wrote:
> And of course I made a typo while copying things into the patch.
> 
> Doing another build test of it now.
> 
> --- vlc-2.2.4.orig/configure.ac   2016-05-31 12:11:07.0 -0400
> +++ vlc-2.2.4/configure.ac2016-11-04 12:22:02.543265439 -0400
> @@ -1422,25 +1422,24 @@
>VLC_SAVE_FLAGS
>AC_CACHE_CHECK([if \$CC groks AltiVec C extensions],
>[ac_cv_c_altivec], [
> -CFLAGS="${CFLAGS} -maltivec"
> +CFLAGS="${CFLAGS} -maltivec -fno-tree-vectorize"
>  AC_COMPILE_IFELSE([AC_LANG_PROGRAM([
>  [#include ]], [
>  [vec_ld(0, (unsigned char *)0);]])], [
> -  ac_cv_c_altivec="-maltivec"
> +  ac_cv_c_altivec="-maltivec -fno-tree-vectorize"
>  ], [
>ac_cv_c_altivec="no"
>  ])
>])
> -  VLC_RESTORE_FLAGS
>AS_IF([test "${ac_cv_c_altivec}" != "no"], [
>  CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"
>  AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec extensions 
> are available.])
> -VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
> -ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
> -VLC_ADD_CFLAGS([deinterlace],[${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}])
> +ALTIVEC_CFLAGS="$ALTIVEC_CFLAGS ${ac_cv_c_altivec} 
> ${ac_cv_c_altivec_abi}"
> +VLC_ADD_CFLAGS([libdeinterlace],[${ac_cv_c_altivec} 
> ${ac_cv_c_altivec_abi}])
>  have_altivec="yes"
>])
>AC_CHECK_HEADERS(altivec.h)
> +  VLC_RESTORE_FLAGS
>  
>VLC_SAVE_FLAGS
>LDFLAGS="${LDFLAGS} -Wl,-framework,vecLib"

That did not quite work, so I had to try the slightly more complicated
patch.

This patch works:

--- vlc-2.2.4.orig/configure.ac 2016-05-31 12:11:07.0 -0400
+++ vlc-2.2.4/configure.ac  2016-11-08 10:28:54.763640362 -0500
@@ -1422,25 +1422,23 @@
   VLC_SAVE_FLAGS
   AC_CACHE_CHECK([if \$CC groks AltiVec C extensions],
   [ac_cv_c_altivec], [
-CFLAGS="${CFLAGS} -maltivec"
+CFLAGS="${CFLAGS} -maltivec -fno-tree-vectorize"
 AC_COMPILE_IFELSE([AC_LANG_PROGRAM([
 [#include ]], [
 [vec_ld(0, (unsigned char *)0);]])], [
-  ac_cv_c_altivec="-maltivec"
+  ac_cv_c_altivec="-maltivec -fno-tree-vectorize"
 ], [
   ac_cv_c_altivec="no"
 ])
   ])
-  VLC_RESTORE_FLAGS
   AS_IF([test "${ac_cv_c_altivec}" != "no"], [
 CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"
 AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec extensions 
are available.])
-VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
-ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
-VLC_ADD_CFLAGS([deinterlace],[${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}])
+ALTIVEC_CFLAGS="$ALTIVEC_CFLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
 have_altivec="yes"
   ])
   AC_CHECK_HEADERS(altivec.h)
+  VLC_RESTORE_FLAGS
 
   VLC_SAVE_FLAGS
   LDFLAGS="${LDFLAGS} -Wl,-framework,vecLib"
--- vlc-2.2.4.orig/modules/video_filter/Modules.am  2015-02-02 
14:42:29.0 -0500
+++ vlc-2.2.4/modules/video_filter/Modules.am   2016-11-08 10:28:31.391639060 
-0500
@@ -29,6 +29,7 @@
 libdeinterlace_plugin_la_SOURCES += deinterlace/merge_arm.S
 libdeinterlace_plugin_la_CFLAGS += -DCAN_COMPILE_ARM
 endif
+libdeinterlace_plugin_la_CFLAGS += $(ALTIVEC_CFLAGS)
 video_filter_LTLIBRARIES += libdeinterlace_plugin.la
 
 libdynamicoverlay_plugin_la_SOURCES = \

With this patch, only functions inside a CPU feature check for altivec
support has any vector instructions.

And I realized the reason it was broken is that when using -maltivec and
-O4 (which vlc uses), you get -ftree-vectorize automatically enabled
which means gcc starts to automatically generate vector instructions
all over the place, which is not desired in this case.  It rather defeats
the purpose of having a cpu feature check after all.

-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

And of course I made a typo while copying things into the patch.

Doing another build test of it now.

--- vlc-2.2.4.orig/configure.ac 2016-05-31 12:11:07.0 -0400
+++ vlc-2.2.4/configure.ac  2016-11-04 12:22:02.543265439 -0400
@@ -1422,25 +1422,24 @@
   VLC_SAVE_FLAGS
   AC_CACHE_CHECK([if \$CC groks AltiVec C extensions],
   [ac_cv_c_altivec], [
-CFLAGS="${CFLAGS} -maltivec"
+CFLAGS="${CFLAGS} -maltivec -fno-tree-vectorize"
 AC_COMPILE_IFELSE([AC_LANG_PROGRAM([
 [#include ]], [
 [vec_ld(0, (unsigned char *)0);]])], [
-  ac_cv_c_altivec="-maltivec"
+  ac_cv_c_altivec="-maltivec -fno-tree-vectorize"
 ], [
   ac_cv_c_altivec="no"
 ])
   ])
-  VLC_RESTORE_FLAGS
   AS_IF([test "${ac_cv_c_altivec}" != "no"], [
 CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"
 AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec extensions 
are available.])
-VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
-ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
-VLC_ADD_CFLAGS([deinterlace],[${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}])
+ALTIVEC_CFLAGS="$ALTIVEC_CFLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
+VLC_ADD_CFLAGS([libdeinterlace],[${ac_cv_c_altivec} 
${ac_cv_c_altivec_abi}])
 have_altivec="yes"
   ])
   AC_CHECK_HEADERS(altivec.h)
+  VLC_RESTORE_FLAGS
 
   VLC_SAVE_FLAGS
   LDFLAGS="${LDFLAGS} -Wl,-framework,vecLib"


-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

Actually maybe this simpler version is better.  I think I just figured
out why libdeinterlace wasn't getting the altivec flags, which was that
it was listed as deinterlace rather than libdeinterlace.

Doing a build test of it now.

--- vlc-2.2.4.orig/configure.ac 2016-05-31 12:11:07.0 -0400
+++ vlc-2.2.4/configure.ac  2016-11-04 12:22:02.543265439 -0400
@@ -1422,25 +1422,24 @@
   VLC_SAVE_FLAGS
   AC_CACHE_CHECK([if \$CC groks AltiVec C extensions],
   [ac_cv_c_altivec], [
-CFLAGS="${CFLAGS} -maltivec"
+CFLAGS="${CFLAGS} -maltivec -fno-vectorize"
 AC_COMPILE_IFELSE([AC_LANG_PROGRAM([
 [#include ]], [
 [vec_ld(0, (unsigned char *)0);]])], [
-  ac_cv_c_altivec="-maltivec"
+  ac_cv_c_altivec="-maltivec -fno-vectorize"
 ], [
   ac_cv_c_altivec="no"
 ])
   ])
-  VLC_RESTORE_FLAGS
   AS_IF([test "${ac_cv_c_altivec}" != "no"], [
 CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"
 AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec extensions 
are available.])
-VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
-ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
-VLC_ADD_CFLAGS([deinterlace],[${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}])
+ALTIVEC_CFLAGS="$ALTIVEC_CFLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
+VLC_ADD_CFLAGS([libdeinterlace],[${ac_cv_c_altivec} 
${ac_cv_c_altivec_abi}])
 have_altivec="yes"
   ])
   AC_CHECK_HEADERS(altivec.h)
+  VLC_RESTORE_FLAGS
 
   VLC_SAVE_FLAGS
   LDFLAGS="${LDFLAGS} -Wl,-framework,vecLib"

-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Sebastian Ramacher]

On 2016-11-03 13:58:58, Lennart Sorensen wrote:
> On Tue, Nov 01, 2016 at 01:42:17PM -0400, Lennart Sorensen wrote:
> > Well that looks like it only adds it for libvlccore.
> 
> So at least something like this is needed, but I think the VLCCORE is
> wrong too, and maybe the deinterlace has to be moved to only merge.c
> rather than all of deinterlace.
> 
> --- configure.ac.orig   2016-11-03 13:56:25.826878272 -0400
> +++ configure.ac2016-11-03 13:56:55.558878272 -0400
> @@ -1431,7 +1431,6 @@
>ac_cv_c_altivec="no"
>  ])
>])
> -  VLC_RESTORE_FLAGS
>AS_IF([test "${ac_cv_c_altivec}" != "no"], [
>  CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"
>  AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec extensions 
> are available.])
> @@ -1441,6 +1440,7 @@
>  have_altivec="yes"
>])
>AC_CHECK_HEADERS(altivec.h)
> +  VLC_RESTORE_FLAGS
>  
>VLC_SAVE_FLAGS
>LDFLAGS="${LDFLAGS} -Wl,-framework,vecLib"
> 
> The CPPFLAGS are being clobbered with the -maltivec, which is only needed
> when testing altivec.h, and should be removed again after that.
> 
> That removes the -maltivec that was showing up everywhere at least, and
> now it is only in a few places, although perhaps still a few too many.

Please get this (and any follow-up patches) integrated upstream. See
https://wiki.videolan.org/Sending_Patches/ for details.

Cheers
-- 
Sebastian Ramacher

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

On Tue, Nov 01, 2016 at 01:42:17PM -0400, Lennart Sorensen wrote:
> Well that looks like it only adds it for libvlccore.

So at least something like this is needed, but I think the VLCCORE is
wrong too, and maybe the deinterlace has to be moved to only merge.c
rather than all of deinterlace.

--- configure.ac.orig   2016-11-03 13:56:25.826878272 -0400
+++ configure.ac2016-11-03 13:56:55.558878272 -0400
@@ -1431,7 +1431,6 @@
   ac_cv_c_altivec="no"
 ])
   ])
-  VLC_RESTORE_FLAGS
   AS_IF([test "${ac_cv_c_altivec}" != "no"], [
 CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"
 AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec extensions 
are available.])
@@ -1441,6 +1440,7 @@
 have_altivec="yes"
   ])
   AC_CHECK_HEADERS(altivec.h)
+  VLC_RESTORE_FLAGS
 
   VLC_SAVE_FLAGS
   LDFLAGS="${LDFLAGS} -Wl,-framework,vecLib"

The CPPFLAGS are being clobbered with the -maltivec, which is only needed
when testing altivec.h, and should be removed again after that.

That removes the -maltivec that was showing up everywhere at least, and
now it is only in a few places, although perhaps still a few too many.

-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

On Tue, Nov 01, 2016 at 07:37:33PM +0200, Adrian Bunk wrote:
> On Tue, Nov 01, 2016 at 01:08:03PM -0400, Lennart Sorensen wrote:
> > On Tue, Nov 01, 2016 at 12:22:19PM -0400, Lennart Sorensen wrote:
> > > On Tue, Nov 01, 2016 at 04:34:01PM +0200, Adrian Bunk wrote:
> > > > This doesn't looks wrong to me.
> > > > 
> > > > Note that depending on the software --enable-altivec can either mean
> > > > - compile unconditionally for AltiVec, or
> > > > - enable AltiVec parts with autodetection to only use them when the
> > > >   hardware supports it
> > > 
> > > Well in VLC it means build with -maltivec among other things.
> > > 
> > > > As I already wrote, vlc contains AltiVec-specific code and 
> > > > autodetection 
> > > > for using it only when the hardware supports it.
> > > > 
> > > > This should be enabled on all ppc ports, except the SPE one.
> > > > 
> > > > --enable-altivec also adding -maltivec elsewhere is a bug.
> > > 
> > > Well it certainly appears to have been done on purpose in the configure
> > > script.  Maybe it is a bug.  Perhaps I should poke it a bit...
> > > 
> > > > And due to this bug the whole AltiVec autodetection in vlc is
> > > > pretty useless.
> > > 
> > > Well if it has such auto detection, then yes it is.
> > 
> > I currently suspect:
> > 
> > configure.ac:
> > ...
> >   ])
> >   VLC_RESTORE_FLAGS
> >   AS_IF([test "${ac_cv_c_altivec}" != "no"], [
> > CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"  <-- this looks wrong
> > AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec 
> > extensions are available.])
> > VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
> > ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} 
> > ${ac_cv_c_altivec_abi}"
> > ...
> > 
> > I think that line should not be there since all over CPPFLAGS is used as
> > part of the COMPILE variable, meaning not just CFLAGS gets -maltivec when
> > needed through ALTIVEC_CFLAGS, but in fact everywhere that has CPPFLAGS
> > gets it, meaning everything.
> 
> I was more suspecting the VLC_ADD_CFLAGS() would be the problem,
> but since the build log says "-maltivec -maltivec" it is actually
> likely that this is wrong in more than one place.

Well that looks like it only adds it for libvlccore.

-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Adrian Bunk]

On Tue, Nov 01, 2016 at 01:08:03PM -0400, Lennart Sorensen wrote:
> On Tue, Nov 01, 2016 at 12:22:19PM -0400, Lennart Sorensen wrote:
> > On Tue, Nov 01, 2016 at 04:34:01PM +0200, Adrian Bunk wrote:
> > > This doesn't looks wrong to me.
> > > 
> > > Note that depending on the software --enable-altivec can either mean
> > > - compile unconditionally for AltiVec, or
> > > - enable AltiVec parts with autodetection to only use them when the
> > >   hardware supports it
> > 
> > Well in VLC it means build with -maltivec among other things.
> > 
> > > As I already wrote, vlc contains AltiVec-specific code and autodetection 
> > > for using it only when the hardware supports it.
> > > 
> > > This should be enabled on all ppc ports, except the SPE one.
> > > 
> > > --enable-altivec also adding -maltivec elsewhere is a bug.
> > 
> > Well it certainly appears to have been done on purpose in the configure
> > script.  Maybe it is a bug.  Perhaps I should poke it a bit...
> > 
> > > And due to this bug the whole AltiVec autodetection in vlc is
> > > pretty useless.
> > 
> > Well if it has such auto detection, then yes it is.
> 
> I currently suspect:
> 
> configure.ac:
> ...
>   ])
>   VLC_RESTORE_FLAGS
>   AS_IF([test "${ac_cv_c_altivec}" != "no"], [
> CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"  <-- this looks wrong
> AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec extensions 
> are available.])
> VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
> ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
> ...
> 
> I think that line should not be there since all over CPPFLAGS is used as
> part of the COMPILE variable, meaning not just CFLAGS gets -maltivec when
> needed through ALTIVEC_CFLAGS, but in fact everywhere that has CPPFLAGS
> gets it, meaning everything.

I was more suspecting the VLC_ADD_CFLAGS() would be the problem,
but since the build log says "-maltivec -maltivec" it is actually
likely that this is wrong in more than one place.

> I will try compile testing that as soon as I have the system ready.

Thanks.

> Len Sorensen

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

On Tue, Nov 01, 2016 at 12:22:19PM -0400, Lennart Sorensen wrote:
> On Tue, Nov 01, 2016 at 04:34:01PM +0200, Adrian Bunk wrote:
> > This doesn't looks wrong to me.
> > 
> > Note that depending on the software --enable-altivec can either mean
> > - compile unconditionally for AltiVec, or
> > - enable AltiVec parts with autodetection to only use them when the
> >   hardware supports it
> 
> Well in VLC it means build with -maltivec among other things.
> 
> > As I already wrote, vlc contains AltiVec-specific code and autodetection 
> > for using it only when the hardware supports it.
> > 
> > This should be enabled on all ppc ports, except the SPE one.
> > 
> > --enable-altivec also adding -maltivec elsewhere is a bug.
> 
> Well it certainly appears to have been done on purpose in the configure
> script.  Maybe it is a bug.  Perhaps I should poke it a bit...
> 
> > And due to this bug the whole AltiVec autodetection in vlc is
> > pretty useless.
> 
> Well if it has such auto detection, then yes it is.

I currently suspect:

configure.ac:
...
  ])
  VLC_RESTORE_FLAGS
  AS_IF([test "${ac_cv_c_altivec}" != "no"], [
CPPFLAGS="${CPPFLAGS} ${ac_cv_c_altivec}"  <-- this looks wrong
AC_DEFINE(CAN_COMPILE_C_ALTIVEC, 1, [Define to 1 if C AltiVec extensions 
are available.])
VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
...

I think that line should not be there since all over CPPFLAGS is used as
part of the COMPILE variable, meaning not just CFLAGS gets -maltivec when
needed through ALTIVEC_CFLAGS, but in fact everywhere that has CPPFLAGS
gets it, meaning everything.

I will try compile testing that as soon as I have the system ready.

-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

On Tue, Nov 01, 2016 at 04:34:01PM +0200, Adrian Bunk wrote:
> This doesn't looks wrong to me.
> 
> Note that depending on the software --enable-altivec can either mean
> - compile unconditionally for AltiVec, or
> - enable AltiVec parts with autodetection to only use them when the
>   hardware supports it

Well in VLC it means build with -maltivec among other things.

> As I already wrote, vlc contains AltiVec-specific code and autodetection 
> for using it only when the hardware supports it.
> 
> This should be enabled on all ppc ports, except the SPE one.
> 
> --enable-altivec also adding -maltivec elsewhere is a bug.

Well it certainly appears to have been done on purpose in the configure
script.  Maybe it is a bug.  Perhaps I should poke it a bit...

> And due to this bug the whole AltiVec autodetection in vlc is
> pretty useless.

Well if it has such auto detection, then yes it is.

-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Adrian Bunk]

On Tue, Nov 01, 2016 at 09:56:45AM -0400, Lennart Sorensen wrote:
> On Mon, Oct 31, 2016 at 11:13:00PM +0200, Adrian Bunk wrote:
> > This actually looks like a bug in upstream configure.ac to me:
> > VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
> > ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} 
> > ${ac_cv_c_altivec_abi}"
> > VLC_ADD_CFLAGS([deinterlace],[${ac_cv_c_altivec} 
> > ${ac_cv_c_altivec_abi}])
> > 
> > It is correct that this adds -maltivec to AltiVec-specific code,
> > and vlc has proper autodetection to run this only when AltiVec
> > is actually present.
> > 
> > The VLC_ADD_CFLAGS here look just wrong - it is not the job of 
> > configure.ac to add such flags to generic code (whatever march
> > and hardware features are present is defined through compiler
> > defaults and the CFLAGS passed by the user).
> 
> Actually what looks really wrong is that debian/rules builds ffmpeg with
> --disable-altivec and then builds vlc with --enable-altivec.

This doesn't looks wrong to me.

Note that depending on the software --enable-altivec can either mean
- compile unconditionally for AltiVec, or
- enable AltiVec parts with autodetection to only use them when the
  hardware supports it

> Since powerpc can't assume you have altivec, perhaps vlc shouldn't be
> built with it, or at least ought to have justification for why it is
> done that way.
>...

As I already wrote, vlc contains AltiVec-specific code and autodetection 
for using it only when the hardware supports it.

This should be enabled on all ppc ports, except the SPE one.

--enable-altivec also adding -maltivec elsewhere is a bug.

And due to this bug the whole AltiVec autodetection in vlc is
pretty useless.

> Len Sorensen

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[luigi burdo]

hi all just to notice

kodi on e5500 2 ghz play without problems and without frame dropping

mkv & mp4 at 1080p without vdpau accelerations.


i suggest to use kodi if vlc crash fo altivec.


Luigi




Da: Lennart Sorensen <lsore...@csclub.uwaterloo.ca>
Inviato: martedì 1 novembre 2016 14.56
A: Adrian Bunk
Cc: James Cowgill; Robert Ou; debian-powe...@lists.debian.org; 
842...@bugs.debian.org
Oggetto: Re: Bug#842513: vlc: immediate crash on launch on powerpc

On Mon, Oct 31, 2016 at 11:13:00PM +0200, Adrian Bunk wrote:
> This actually looks like a bug in upstream configure.ac to me:
> VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
> ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
> VLC_ADD_CFLAGS([deinterlace],[${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}])
>
> It is correct that this adds -maltivec to AltiVec-specific code,
> and vlc has proper autodetection to run this only when AltiVec
> is actually present.
>
> The VLC_ADD_CFLAGS here look just wrong - it is not the job of
> configure.ac to add such flags to generic code (whatever march
> and hardware features are present is defined through compiler
> defaults and the CFLAGS passed by the user).

Actually what looks really wrong is that debian/rules builds ffmpeg with
--disable-altivec and then builds vlc with --enable-altivec.

Since powerpc can't assume you have altivec, perhaps vlc shouldn't be
built with it, or at least ought to have justification for why it is
done that way.  Maybe it was thought that no CPU without altivec would
be powerful enough to bother using vlc, but I think that may not in fact
be a valid assumption these days.

Certainly a 2.5GHz e5500 core is pretty decent performance, but has
no altivec.

--
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Lennart Sorensen]

On Mon, Oct 31, 2016 at 11:13:00PM +0200, Adrian Bunk wrote:
> This actually looks like a bug in upstream configure.ac to me:
> VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
> ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
> VLC_ADD_CFLAGS([deinterlace],[${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}])
> 
> It is correct that this adds -maltivec to AltiVec-specific code,
> and vlc has proper autodetection to run this only when AltiVec
> is actually present.
> 
> The VLC_ADD_CFLAGS here look just wrong - it is not the job of 
> configure.ac to add such flags to generic code (whatever march
> and hardware features are present is defined through compiler
> defaults and the CFLAGS passed by the user).

Actually what looks really wrong is that debian/rules builds ffmpeg with
--disable-altivec and then builds vlc with --enable-altivec.

Since powerpc can't assume you have altivec, perhaps vlc shouldn't be
built with it, or at least ought to have justification for why it is
done that way.  Maybe it was thought that no CPU without altivec would
be powerful enough to bother using vlc, but I think that may not in fact
be a valid assumption these days.

Certainly a 2.5GHz e5500 core is pretty decent performance, but has
no altivec.

-- 
Len Sorensen

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: Re: Bug#842513: vlc: immediate crash on launch on powerpc

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 vlc: configure.ac altivec setting broken
Bug #842513 [src:vlc] vlc: should prevent installation on powerpc G3
Changed Bug title to 'vlc: configure.ac altivec setting broken' from 'vlc: 
should prevent installation on powerpc G3'.

-- 
842513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Adrian Bunk]

Control: retitle -1 vlc: configure.ac altivec setting broken

On Sun, Oct 30, 2016 at 11:40:50AM +, James Cowgill wrote:
>...
> On 30/10/16 00:16, Robert Ou wrote:
> > On Sat, Oct 29, 2016 at 3:43 PM, James Cowgill  wrote:
> >> Control: tags -1 help
> >> Control: severity -1 grave
> >>
> >> Hi,
> >>
> >> On 29/10/16 23:00, Robert Ou wrote:
> >>> Package: src:vlc
> >>> Version: 2.2.4-7
> >>> Severity: normal
> >>>
> >>> Dear Maintainer,
> >>>
> >>> I decided I wanted to test the performance of Debian PowerPC on my
> >>> ancient iMac, and I discovered that vlc will immediately crash with an
> >>> illegal instruction right after showing the "Privacy and Network Access
> >>> Policy" window and before showing the main window. The crashes look like
> >>> the following:
> >>>
> >>> [ 1560.952016] vlc[997]: unhandled signal 4 at 0ea48f58 nip 0ea48f58 lr 
> >>> 0ea48f4c code 30001
> >>
> >> As powerpc is a release architecture, this bug is RC.
> >>
> >> I tried running vlc on partch. It managed to get further, but then
> >> segfaulted inside QT so it's probably a separate issue. I also had to
> >> run it in xvfb so it probably gets different results.
> >>
> >> Specifically what powerpc hardware do you have? Could you run vlc within
> >> gdb to determine which instruction it SIGILLs on (try 'layout asm')?
> > 
> > I was testing on a first-generation iMac with a 333 MHz PowerPC 750
> > (G3). Running vlc under gdb shows that the crash occurs in
> > libqt4_plugin.so in QRect::adjusted. The crash occurs on a "lvx
> > v0,r10,r5" opcode, which is an Altivec opcode. The G3 however does not
> > support Altivec. Here is a backtrace and some more debug information:
> 
> This explains it. From the PowerPC FAQ:
> https://wiki.debian.org/PowerPC/FAQ#VLC_crashes_on_startup._What.27s_up_with_that.3F
> 
> "
> If VLC immediately crashes, it's probably because you're on a G3 and
> VLC was compiled with Altivec instructions. To use VLC on a G3, you
> must compile it with the configure option --disable-altivec.
> "
> 
> Having said that, I think adding something to vlc's preinst to prevent
> installation on systems without altivec would be a good idea here.
>...

This actually looks like a bug in upstream configure.ac to me:
VLC_ADD_CFLAGS([libvlccore],[${ac_cv_c_altivec}])
ALTIVEC_CFLAGS="$ALTIVEC_FLAGS ${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}"
VLC_ADD_CFLAGS([deinterlace],[${ac_cv_c_altivec} ${ac_cv_c_altivec_abi}])

It is correct that this adds -maltivec to AltiVec-specific code,
and vlc has proper autodetection to run this only when AltiVec
is actually present.

The VLC_ADD_CFLAGS here look just wrong - it is not the job of 
configure.ac to add such flags to generic code (whatever march
and hardware features are present is defined through compiler
defaults and the CFLAGS passed by the user).

> Thanks,
> James

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Robert Ou]

On Sun, Oct 30, 2016 at 4:40 AM, James Cowgill  wrote:
> Control: tags -1 - help
> Control: severity -1 important
> Control: retitle -1 vlc: should prevent installation on powerpc G3
>
> Hi,
>
> On 30/10/16 00:16, Robert Ou wrote:
>> On Sat, Oct 29, 2016 at 3:43 PM, James Cowgill  wrote:
>>> Control: tags -1 help
>>> Control: severity -1 grave
>>>
>>> Hi,
>>>
>>> On 29/10/16 23:00, Robert Ou wrote:
 Package: src:vlc
 Version: 2.2.4-7
 Severity: normal

 Dear Maintainer,

 I decided I wanted to test the performance of Debian PowerPC on my
 ancient iMac, and I discovered that vlc will immediately crash with an
 illegal instruction right after showing the "Privacy and Network Access
 Policy" window and before showing the main window. The crashes look like
 the following:

 [ 1560.952016] vlc[997]: unhandled signal 4 at 0ea48f58 nip 0ea48f58 lr 
 0ea48f4c code 30001
>>>
>>> As powerpc is a release architecture, this bug is RC.
>>>
>>> I tried running vlc on partch. It managed to get further, but then
>>> segfaulted inside QT so it's probably a separate issue. I also had to
>>> run it in xvfb so it probably gets different results.
>>>
>>> Specifically what powerpc hardware do you have? Could you run vlc within
>>> gdb to determine which instruction it SIGILLs on (try 'layout asm')?
>>
>> I was testing on a first-generation iMac with a 333 MHz PowerPC 750
>> (G3). Running vlc under gdb shows that the crash occurs in
>> libqt4_plugin.so in QRect::adjusted. The crash occurs on a "lvx
>> v0,r10,r5" opcode, which is an Altivec opcode. The G3 however does not
>> support Altivec. Here is a backtrace and some more debug information:
>
> This explains it. From the PowerPC FAQ:
> https://wiki.debian.org/PowerPC/FAQ#VLC_crashes_on_startup._What.27s_up_with_that.3F
>
> "
> If VLC immediately crashes, it's probably because you're on a G3 and
> VLC was compiled with Altivec instructions. To use VLC on a G3, you
> must compile it with the configure option --disable-altivec.
> "
>
> Having said that, I think adding something to vlc's preinst to prevent
> installation on systems without altivec would be a good idea here.
>
> I'm not sure going through all the trouble of compiling vlc twice so it
> works on the G3 is worth it here - especially since powerpc may not be
> a release architecture in 24 hours...
>

Sorry, I completely missed that FAQ entry amongst the other random
bugs/quirks listed there. I am totally fine with not having vlc on
this system (I didn't expect vlc to actually be able to play anything
at a reasonable speed on this ancient a system). However, will
blacklisting it in the preinst step break packages like
task-xfce-desktop or break people who already had vlc installed and
tried to upgrade?

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[James Cowgill]

Control: tags -1 - help
Control: severity -1 important
Control: retitle -1 vlc: should prevent installation on powerpc G3

Hi,

On 30/10/16 00:16, Robert Ou wrote:
> On Sat, Oct 29, 2016 at 3:43 PM, James Cowgill  wrote:
>> Control: tags -1 help
>> Control: severity -1 grave
>>
>> Hi,
>>
>> On 29/10/16 23:00, Robert Ou wrote:
>>> Package: src:vlc
>>> Version: 2.2.4-7
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>> I decided I wanted to test the performance of Debian PowerPC on my
>>> ancient iMac, and I discovered that vlc will immediately crash with an
>>> illegal instruction right after showing the "Privacy and Network Access
>>> Policy" window and before showing the main window. The crashes look like
>>> the following:
>>>
>>> [ 1560.952016] vlc[997]: unhandled signal 4 at 0ea48f58 nip 0ea48f58 lr 
>>> 0ea48f4c code 30001
>>
>> As powerpc is a release architecture, this bug is RC.
>>
>> I tried running vlc on partch. It managed to get further, but then
>> segfaulted inside QT so it's probably a separate issue. I also had to
>> run it in xvfb so it probably gets different results.
>>
>> Specifically what powerpc hardware do you have? Could you run vlc within
>> gdb to determine which instruction it SIGILLs on (try 'layout asm')?
> 
> I was testing on a first-generation iMac with a 333 MHz PowerPC 750
> (G3). Running vlc under gdb shows that the crash occurs in
> libqt4_plugin.so in QRect::adjusted. The crash occurs on a "lvx
> v0,r10,r5" opcode, which is an Altivec opcode. The G3 however does not
> support Altivec. Here is a backtrace and some more debug information:

This explains it. From the PowerPC FAQ:
https://wiki.debian.org/PowerPC/FAQ#VLC_crashes_on_startup._What.27s_up_with_that.3F

"
If VLC immediately crashes, it's probably because you're on a G3 and
VLC was compiled with Altivec instructions. To use VLC on a G3, you
must compile it with the configure option --disable-altivec.
"

Having said that, I think adding something to vlc's preinst to prevent
installation on systems without altivec would be a good idea here.

I'm not sure going through all the trouble of compiling vlc twice so it
works on the G3 is worth it here - especially since powerpc may not be
a release architecture in 24 hours...

Thanks,
James



signature.asc
Description: OpenPGP digital signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: Re: Bug#842513: vlc: immediate crash on launch on powerpc

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - help
Bug #842513 [src:vlc] vlc: immediate crash on launch on powerpc
Removed tag(s) help.
> severity -1 important
Bug #842513 [src:vlc] vlc: immediate crash on launch on powerpc
Severity set to 'important' from 'grave'
> retitle -1 vlc: should prevent installation on powerpc G3
Bug #842513 [src:vlc] vlc: immediate crash on launch on powerpc
Changed Bug title to 'vlc: should prevent installation on powerpc G3' from 
'vlc: immediate crash on launch on powerpc'.

-- 
842513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Robert Ou]

On Sat, Oct 29, 2016 at 3:43 PM, James Cowgill  wrote:
> Control: tags -1 help
> Control: severity -1 grave
>
> Hi,
>
> On 29/10/16 23:00, Robert Ou wrote:
>> Package: src:vlc
>> Version: 2.2.4-7
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> I decided I wanted to test the performance of Debian PowerPC on my
>> ancient iMac, and I discovered that vlc will immediately crash with an
>> illegal instruction right after showing the "Privacy and Network Access
>> Policy" window and before showing the main window. The crashes look like
>> the following:
>>
>> [ 1560.952016] vlc[997]: unhandled signal 4 at 0ea48f58 nip 0ea48f58 lr 
>> 0ea48f4c code 30001
>
> As powerpc is a release architecture, this bug is RC.
>
> I tried running vlc on partch. It managed to get further, but then
> segfaulted inside QT so it's probably a separate issue. I also had to
> run it in xvfb so it probably gets different results.
>
> Specifically what powerpc hardware do you have? Could you run vlc within
> gdb to determine which instruction it SIGILLs on (try 'layout asm')?

I was testing on a first-generation iMac with a 333 MHz PowerPC 750
(G3). Running vlc under gdb shows that the crash occurs in
libqt4_plugin.so in QRect::adjusted. The crash occurs on a "lvx
v0,r10,r5" opcode, which is an Altivec opcode. The G3 however does not
support Altivec. Here is a backtrace and some more debug information:

0x0ea11f58 in QRect::adjusted (yp2=-5, xp2=-5, yp1=4, xp1=4,
this=0xaf3fd6f0) at
/usr/include/powerpc-linux-gnu/qt5/QtCore/qrect.h:382
382/usr/include/powerpc-linux-gnu/qt5/QtCore/qrect.h: No such file
or directory.
(gdb) where
#0  0x0ea11f58 in QRect::adjusted (yp2=-5, xp2=-5, yp1=4, xp1=4,
this=0xaf3fd6f0) at
/usr/include/powerpc-linux-gnu/qt5/QtCore/qrect.h:382
#1  AbstractController::telexFrame (this=this@entry=0xae05c8c0) at
components/controller.cpp:649
#2  0x0ea13c1c in AbstractController::createWidget
(this=this@entry=0xae05c8c0, button=button@entry=TELETEXT_BUTTONS,
options=0) at components/controller.cpp:376
#3  0x0ea16dd0 in AbstractController::createAndAddWidget
(this=this@entry=0xae05c8c0,
controlLayout_=controlLayout_@entry=0xae05c930,
i_index=i_index@entry=-1, i_type=i_type@entry=TELETEXT_BUTTONS,
i_option=) at components/controller.cpp:181
#4  0x0ea17920 in AbstractController::parseAndCreate
(newControlLayout=0xae05c930, config=..., this=0xae05c8c0) at
components/controller.cpp:145
#5  ControlsWidget::ControlsWidget (this=0xae05c8c0, _p_i=, b_advControls=, _parent=) at
components/controller.cpp:700
#6  0x0e934110 in MainInterface::createMainWidget
(this=this@entry=0xaf240990, creationSettings=0xaf2306a0) at
main_interface.cpp:491
#7  0x0e934b0c in MainInterface::MainInterface (this=0xaf240990,
_p_intf=) at main_interface.cpp:166
#8  0x0e91b8a4 in Thread (obj=0x100c3d30) at qt4.cpp:532
#9  0x0ff73500 in start_thread (arg=0xaf3fe380) at pthread_create.c:335
#10 0x0fe8a9ac in clone () at
../sysdeps/unix/sysv/linux/powerpc/powerpc32/clone.S:91
(gdb) x/16i $pc-32
   0xea11f38 :mr  r3,r14
   0xea11f3c :bl  0xead3400
   0xea11f40 :mr  r4,r23
   0xea11f44 :addir3,r1,320
   0xea11f48 :bl  0xead3860
   0xea11f4c :lwz r4,-32472(r30)
   0xea11f50 :addir10,r1,464
   0xea11f54 :li  r5,-144
=> 0xea11f58 :lvx v0,r10,r5
   0xea11f5c :li  r14,-128
   0xea11f60 :mr  r3,r21
   0xea11f64 :lvx v1,0,r4
   0xea11f68 :mr  r4,r26
   0xea11f6c :vadduwm v0,v0,v1
   0xea11f70 :stvxv0,r10,r14
   0xea11f74 :bl  0xeac09b0
(gdb) info reg
r0 0xea11f40245440320
r1 0xaf3fd5b02940196272
r2 0xaf4058502940229712
r3 0xaf3fd6f02940196592
r4 0xeb0b790246462352
r5 0xff704294967152
r6 0xa0d2763c2698147388
r7 0x00
r8 0x00
r9 0x1925
r100xaf3fd7802940196736
r110xdd4c9f0232049136
r120xfe1eac4266463940
r130x100280a0268599456
r140xaf3fd6582940196440
r150xae0659502919651664
r160xaf3fd75c2940196700
r170xae06d6102919683600
r180xae071b602919701344
r190xaf3fd6482940196424
r20

Processed: Re: Bug#842513: vlc: immediate crash on launch on powerpc

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #842513 [src:vlc] vlc: immediate crash on launch on powerpc
Added tag(s) help.
> severity -1 grave
Bug #842513 [src:vlc] vlc: immediate crash on launch on powerpc
Severity set to 'grave' from 'normal'

-- 
842513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[James Cowgill]

Control: tags -1 help
Control: severity -1 grave

Hi,

On 29/10/16 23:00, Robert Ou wrote:
> Package: src:vlc
> Version: 2.2.4-7
> Severity: normal
> 
> Dear Maintainer,
> 
> I decided I wanted to test the performance of Debian PowerPC on my
> ancient iMac, and I discovered that vlc will immediately crash with an
> illegal instruction right after showing the "Privacy and Network Access
> Policy" window and before showing the main window. The crashes look like
> the following:
> 
> [ 1560.952016] vlc[997]: unhandled signal 4 at 0ea48f58 nip 0ea48f58 lr 
> 0ea48f4c code 30001

As powerpc is a release architecture, this bug is RC.

I tried running vlc on partch. It managed to get further, but then
segfaulted inside QT so it's probably a separate issue. I also had to
run it in xvfb so it probably gets different results.

Specifically what powerpc hardware do you have? Could you run vlc within
gdb to determine which instruction it SIGILLs on (try 'layout asm')?

Can a powerpc porter help here?

Thanks,
James



signature.asc
Description: OpenPGP digital signature
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#842513: vlc: immediate crash on launch on powerpc

[Robert Ou]

Package: src:vlc
Version: 2.2.4-7
Severity: normal

Dear Maintainer,

I decided I wanted to test the performance of Debian PowerPC on my
ancient iMac, and I discovered that vlc will immediately crash with an
illegal instruction right after showing the "Privacy and Network Access
Policy" window and before showing the main window. The crashes look like
the following:

[ 1560.952016] vlc[997]: unhandled signal 4 at 0ea48f58 nip 0ea48f58 lr 
0ea48f4c code 30001
[ 1619.049833] vlc[1022]: unhandled signal 4 at 0ea48f58 nip 0ea48f58 lr 
0ea48f4c code 30001
[ 1663.893708] vlc[1033]: unhandled signal 4 at 0ea48f58 nip 0ea48f58 lr 
0ea48f4c code 30001
[ 1903.151117] vlc[1425]: unhandled signal 4 at 0ea11f58 nip 0ea11f58 lr 
0ea11f4c code 30001
[ 2286.635504] vlc[1525]: unhandled signal 4 at 0ea11f58 nip 0ea11f58 lr 
0ea11f4c code 30001
[ 2422.735693] vlc[1589]: unhandled signal 4 at 0ea11f58 nip 0ea11f58 lr 
0ea11f4c code 30001
[ 2475.942685] vlc[1599]: unhandled signal 4 at 0ea11f58 nip 0ea11f58 lr 
0ea11f4c code 30001

The output of "vlc -vvv" is also attached.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 4.7.0-1-powerpc
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages vlc depends on:
ii  dpkg 1.18.10
ii  vlc-bin  2.2.4-7
ii  vlc-l10n 2.2.4-7
ii  vlc-plugin-base  2.2.4-7
ii  vlc-plugin-qt2.2.4-7
ii  vlc-plugin-video-output  2.2.4-7

Versions of packages vlc recommends:
ii  vlc-plugin-notify  2.2.4-7
ii  vlc-plugin-samba   2.2.4-7
ii  vlc-plugin-skins2  2.2.4-7
ii  vlc-plugin-video-splitter  2.2.4-7
ii  vlc-plugin-visualization   2.2.4-7

vlc suggests no packages.

Versions of packages libvlc5 depends on:
ii  dpkg 1.18.10
ii  libc62.24-5
ii  libvlccore8  2.2.4-7

Versions of packages libvlc5 recommends:
ii  libvlc-bin  2.2.4-7

Versions of packages libvlccore8 depends on:
ii  dpkg 1.18.10
ii  libc62.24-5
ii  libdbus-1-3  1.10.12-1
ii  libidn11 1.33-1

Versions of packages libvlccore8 recommends:
ii  libproxy-tools  0.4.11-5

Versions of packages vlc-plugin-notify depends on:
ii  dpkg1.18.10
ii  libc6   2.24-5
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.1-1
ii  libgtk2.0-0 2.24.31-1
ii  libnotify4  0.7.7-1
ii  libvlccore8 2.2.4-7

-- no debconf information
[10382970] core libvlc debug: VLC media player - 2.2.4 Weatherwax
[10382970] core libvlc debug: Copyright © 1996-2016 the VideoLAN team
[10382970] core libvlc debug: revision 2.2.3-37-g888b7e89
[10382970] core libvlc debug: configured with ./configure  
'--build=powerpc-linux-gnu' '--prefix=/usr' '--includedir=${prefix}/include' 
'--mandir=${prefix}/share/man' '--infodir=${prefix}/share/info' 
'--sysconfdir=/etc' '--localstatedir=/var' '--disable-silent-rules' 
'--libdir=${prefix}/lib/powerpc-linux-gnu' 
'--libexecdir=${prefix}/lib/powerpc-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--config-cache' '--disable-update-check' 
'--enable-fast-install' '--docdir=/usr/share/doc/vlc-data' 
'--with-binary-version=2.2.4-7' '--enable-a52' '--enable-aa' '--enable-bluray' 
'--enable-bonjour' '--enable-caca' '--enable-chromaprint' '--enable-dbus' 
'--enable-dca' '--enable-directfb' '--enable-dvbpsi' '--enable-dvdnav' 
'--enable-faad' '--enable-flac' '--enable-fluidsynth' '--enable-freerdp' 
'--enable-freetype' '--enable-fribidi' '--enable-gles1' '--enable-gles2' 
'--enable-gnutls' '--enable-jack' '--enable-kate' '--enable-libass' 
'--enable-libmpeg2' '--enable-libxml2' '--enable-lirc' '--enable-live555' 
'--enable-mad' '--enable-mkv' '--enable-mod' '--enable-mpc' '--enable-mtp' 
'--enable-mux_ogg' '--enable-ncurses' '--enable-notify' '--enable-ogg' 
'--enable-opus' '--enable-pulse' '--enable-qt' '--enable-realrtsp' 
'--enable-samplerate' '--enable-schroedinger' '--enable-sdl' 
'--enable-sdl-image' '--enable-sftp' '--enable-shine' '--enable-shout' 
'--enable-skins2' '--enable-sndio' '--enable-speex' '--enable-svg' 
'--enable-svgdec' '--enable-taglib' '--enable-theora' '--enable-twolame' 
'--enable-upnp' '--enable-vcdx' '--enable-vdpau' '--enable-vnc' 
'--enable-vorbis' '--enable-x264' '--enable-x265' '--enable-zvbi' 
'--with-kde-solid=/usr/share/solid/actions/' '--disable-decklink' 
'--disable-dxva2' '--disable-fdkaac' '--disable-gnomevfs' '--disable-goom' 
'--disable-gst-decode' '--disable-libtar' '--disable-mfx' '--disable-opencv' 
'--disable-projectm' '--disable-telx' '--disable-vpx' '--disable-vsxu' 
'--disable-wasapi' '--enable-alsa' '--enable-atmo' '--enable-dc1394' 
'--enable-dv1394' '--enable-linsys' '--enable-omxil' '--enable-udev' 
'--enable-v4l2' '--enable-libva' '--enable-vcd' '--enable-smbclient' 
'--disable-oss'