Bug#908549: Debug data! (Was: gimp: Bug#924448: segfault when using measuring tool)

Tue Mar 19 19:37:26 GMT 2019

Hi Bernhard,

Thank you very much for sharing your clever debug
fu!

I tried it.

I'm happy to report your advice elicited a stack
trace like the one in bug report #908549.

It's OK with me if you merge my <cough> stupendous
bug report, #924448, with it.

Plus, if it would be comfortable, convenient, and
all those good things, feel free to share any
thoughts you may happen to have on how I might
reconcile why

    1.) Frederic MASSOT wrote

            "The fix is built-in for versions 2.10"

        at

            https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908549#20

    2.) but version 2.10.8-2 of debian's gimp
        package seems to still have the same bug?

Thank you again for maintaining gimp and sharing
your considerable skills so freely.

Both are fine qualities!

So,
Kingsley

PS: For what it's worth, details of what I tried
follows.

    root:~ aptitude install gimp-dbgsym libglib2.0-0-dbgsym

    km:~ script -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'run' -ex 'bt' -ex 'detach' -ex 'quit' --args gimp" -a gdb_gimp_$(date +%Y-%m-%d_%H-%M-%S).log

Its output is the first file attached to this email.

Maybe we agree it has less of a back trace.

Next, I installed the systemd-coredump package.

    root:~ aptitude install systemd-coredump

re-ran gimp,

    km:~ gimp

    ( create a new image

      select the measure tool

      left click on the new image

      wait a few seconds, and.....

      kaBOOM! )

and found a cool new core!

    root:~ coredumpctl list
    TIME                            PID   UID   GID SIG COREFILE  EXE
    Tue 2019-03-19 11:27:04 PDT   20581  1000  1000  11 present   /usr/bin/gimp-2.10

    root:~ coredumpctl gdb 20581

    coredumpctl's output is in the second file
    attached to this email.

It looks to me like the main stack trace (of
thread 20581) reveals frames

    g_closure_invoke (libgobject-2.0.so.0)
    signal_emit_unlocked_R (libgobject-2.0.so.0)
    g_signal_emit_valist (libgobject-2.0.so.0)
    g_signal_emit (libgobject-2.0.so.0)
    gimp_tool_widget_changed (gimp-2.10)
    g_object_notify_by_spec_internal (libgobject-2.0.so.0)
    gimp_tool_compass_update_angle (gimp-2.10)
    gimp_tool_compass_changed (gimp-2.10)

like in your email for the similar bug report at

    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908549#10

Plus, much as you astutely asked yesterday, yes,
they do repeat.

8 times.

On 03/19/2019 14:28, Bernhard Übelacker wrote:
> Hello Kingsley G. Morse Jr.,
> 
> 
> > My main concern?>> The normal way of eliciting a back trace from> within gdb didn't work.> > The non repeating lines were reported by defining> a function in gdb and logging output to a file.
> 
> You can start gimp that way to get a backtrace:
> 
>     script -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'run' -ex 'bt' -ex 'detach' -ex 'quit' --args gimp" -a gdb_gimp_$(date +%Y-%m-%d_%H-%M-%S).log
> 
> This gave me a 11MB file, so it took some time
> for gdb to finish to write the 68000 stack frames.
> 
> Another alternative is to install a coredump collector
> like systemd-coredump. After that you should be able to
> list collected core dumps of the current boot by:
> 
>     coredumpctl list
> 
> And have that core dump loaded into gdb by:
> 
>     coredumpctl gdb <PID>
> 
> Both may lead to better results if you have debug
> symbols installed like described in [1].
> In this case packages gimp-dbgsym libglib2.0-0-dbgsym.
> 
> For debugging graphical applications it may also be convenient
> to ssh into the target machine if a second computer is available,
> or at least start gdb from the "ctl-alt-F1 old school console".
> 
> This can be combined with running gdb inside tmux in the graphical
> environment and, if keyboard gets locked, ctl-alt-F1 and 'tmux attach'
> to access the locked gdb. And if the tmux step was missed, it may be
> possible to "move" the locked gdb process to another terminal ...
> 
> Happy debugging. :-)
> 
> Kind regards,
> Bernhard
> 
> [1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

-- 
Time is the fire in which we all burn.

-------------- next part --------------
Script started on 2019-03-19 11:11:34-0700
Reading symbols from gimp...Reading symbols from /usr/lib/debug/.build-id/5a/56cddb418553f4e42eb66a0c9148bb7543ddcd.debug...done.
done.
Starting program: /usr/bin/gimp 
BFD: /usr/lib/debug/.build-id/da/c552d8815d9a4ef5d055ab6cd81e0478998e2c.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/da/c552d8815d9a4ef5d055ab6cd81e0478998e2c.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/da/c552d8815d9a4ef5d055ab6cd81e0478998e2c.debug" has no build-id, file skipped
BFD: /usr/lib/debug/.build-id/e5/02ab31fa523af198980f0f57ccb2949798ec9d.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/e5/02ab31fa523af198980f0f57ccb2949798ec9d.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/e5/02ab31fa523af198980f0f57ccb2949798ec9d.debug" has no build-id, file skipped
BFD: /usr/lib/debug/.build-id/41/f29963806d55346284ccbbbff7ce1568c05a4b.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/41/f29963806d55346284ccbbbff7ce1568c05a4b.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/41/f29963806d55346284ccbbbff7ce1568c05a4b.debug" has no build-id, file skipped
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
BFD: /usr/lib/debug/.build-id/c8/2785938ed49369549f97c435a2164d5537d787.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/c8/2785938ed49369549f97c435a2164d5537d787.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/c8/2785938ed49369549f97c435a2164d5537d787.debug" has no build-id, file skipped
BFD: /usr/lib/debug/.build-id/b4/8ee7d166852be63462d6a8f2d1599b6c65a89d.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/b4/8ee7d166852be63462d6a8f2d1599b6c65a89d.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/b4/8ee7d166852be63462d6a8f2d1599b6c65a89d.debug" has no build-id, file skipped
BFD: /usr/lib/debug/.build-id/b0/929a0b74877b19ff6ae956d9c3a23b2211d39e.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/b0/929a0b74877b19ff6ae956d9c3a23b2211d39e.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/b0/929a0b74877b19ff6ae956d9c3a23b2211d39e.debug" has no build-id, file skipped
BFD: /usr/lib/debug/.build-id/b1/1e8718bce950a16015ee80c15c6b488369fb38.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/b1/1e8718bce950a16015ee80c15c6b488369fb38.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/b1/1e8718bce950a16015ee80c15c6b488369fb38.debug" has no build-id, file skipped
[New Thread 0xb5d28b40 (LWP 18239)]
BFD: /usr/lib/debug/.build-id/ff/9a2994397cf6d0556c3eff4084392dc31eb2a7.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/ff/9a2994397cf6d0556c3eff4084392dc31eb2a7.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/ff/9a2994397cf6d0556c3eff4084392dc31eb2a7.debug" has no build-id, file skipped
[New Thread 0xb4205b40 (LWP 18242)]
[New Thread 0xb3a04b40 (LWP 18243)]
BFD: /usr/lib/debug/.build-id/3e/91fc79df7ef64213ada45340cd54a7d110a90f.debug: unable to initialize decompress status for section .debug_aranges
BFD: /usr/lib/debug/.build-id/3e/91fc79df7ef64213ada45340cd54a7d110a90f.debug: unable to initialize decompress status for section .debug_aranges
warning: File "/usr/lib/debug/.build-id/3e/91fc79df7ef64213ada45340cd54a7d110a90f.debug" has no build-id, file skipped
[New Thread 0xa9cdfb40 (LWP 18248)]
[New Thread 0xa94deb40 (LWP 18249)]
[New Thread 0xa8cddb40 (LWP 18250)]
[New Thread 0xa71c0b40 (LWP 18251)]
[Thread 0xa71c0b40 (LWP 18251) exited]
/usr/bin/gimp: LibGimpBase-WARNING: gimp: gimp_wire_read(): error
GIMP-Error: Unable to run plug-in "plugin-resynth-sharpen.py"
(/usr/lib/gimp/2.0/plug-ins/plugin-resynth-sharpen.py)