Re: [Gimp-developer] Gimp GIT and GEGL GIT = segment fault

[Øyvind Kolås <pippin gimp org>]

On Thu, Dec 28, 2017 at 5:31 PM, Helmut Jarausch <jarausch skynet be> wrote:
> I'm using gimp and gegl's GIT version.
> Both versions from 2017/12/26 work just fine.
>
> But with Gegl GIT (2017/12/28) and the unchanged Gimp (2017/12/26)
> I get a crash while just scrolling an image in Gimp.

It doesn't crash for me - and thus far no reports on IRC in #gimp.

> The backtrace gives:
> gimp: fatal error: Segmentation fault
> gimp (pid:30588): [E]xit, [H]alt, show [S]tack trace or [P]roceed: S
> #0  0x00007fb678b09d40 in waitpid () from /lib64/libpthread.so.0
> #1  0x00007fb6794a1150 in g_on_error_stack_trace (
> #2  0x00007fb6794a102b in g_on_error_query (prg_name=0x5627bc3bc470 "gimp")
> #3  0x00005627bb603d52 in gimp_eek (reason=0x5627bbb18517 "fatal error",
> #4  0x00005627bb603b43 in gimp_fatal_error (
> #5  0x00005627bb604a30 in gimp_sigfatal_handler (sig_num=11) at signals.c:96
> #6  <signal handler called>
> #7  0x00007fb67a72ae50 in gegl_buffer_iterate_read_simple ()
> #8  0x000000d600000080 in ?? ()
> #9  0x0000000000000000 in ?? ()
> gimp (pid:30588): [E]xit, [H]alt, show [S]tack trace or [P]roceed:
>
> Can anybody reproduce this? If not, what can I do to help locating the bug?
>
> I'm using gcc-7.2.0.

Figuring out which particular commit of the commits making changes to
gegl/buffer/gegl-buffer-access introduces the crash would be helpful,
it shouldn't even need a git bisect - and you can do the make && sudo
make install from within the gegl subdir in GEGL to avoid also having
to rebuild all operations. On my system it doesn't crash, which image
precision (bitdepth) is it crashing for, and using what
cpu/distro/kernel?

/pippin - http://pippin.gimp.org/