[FFmpeg-trac] #5231(avcodec:new): Crashes in ff_deblock_v_luma_8_sse2

[FFmpeg]

#5231: Crashes in ff_deblock_v_luma_8_sse2
-------------------------------------+-------------------------------------
             Reporter:  mi           |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  avcodec
              Version:  unspecified  |               Resolution:
             Keywords:  h264 crash   |               Blocked By:
  SIGSEGV                            |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by cehoyos):

 Replying to [comment:14 mi]:
 > Replying to [comment:12 cehoyos]:
 > > How is the new attachment different from the last one you attached?
 > It was obtained using binaries built with an additional
 `configure`-argument: `--disable-stripping`. As a result, it may contain
 additional information to help ffmpeg-developers figure out, what is
 wrong.

 No, shared libraries are not stripped by default. Only useless labels that
 gdb cannot parse correctly are removed from compiled yasm source files.

 > Replying to [comment:13 cehoyos]:
 > > I had not realized you are a packager
 >
 > I happen to be a member of the FreeBSD ports-team. However, I do not
 maintain the ffmpeg-port(s).
 >
 > > > `--enable-nonfree`
 > > Where does this option come from?
 >
 > The FreeBSD port http://www.freshports.org/multimedia/ffmpeg has a
 number of build-time options, enabling the stricter-licensed parts being
 one of them (`NONFREE`). As you can see from the above-linked port-page,
 the option is ''off'' by default so the ''binary''-distribution remains
 properly licensed.
 >
 > On my own systems, where I build everything from source (using ports
 maintained by myself and fellow ports-maintainers), I enable this option.

 Thank you for the explanation.
 Please understand that generally tests with sane configure lines are
 required (although I don't know if it makes any difference for this
 ticket): I will comment in ticket #5234.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/5231#comment:15>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker