• Jehan's avatar
    app, tools: use the new gimp_print_stack_trace() to output the... · 8d2ae895
    Jehan authored
    ... stacktrace into a file on non-Win32 systems.
    This has a few advantages:
    - First, we don't need to duplicate stacktrace code inside the
      independent gimp-debug-tool (I even noticed that the version in the
      tool was gdb-only and not updated for lldb fallback; proof that code
      duplication is evil!). Instead, even on a crash, we can create the
      stacktrace from the main binary and simply pass it as a file.
    - Secondly, that allows to fallback to the backtrace() API even for
      crashes (this was not possible if the backtrace was done from a
      completely different process). That's nice because this makes that we
      will always get backtraces in Linux (even though backtrace() API is
      not as nice as gdb/lldb, it's better than nothing).
    - Finally this makes the code smaller (i.e. easier to maintain), more
      consistent and similar on all platforms.
    8d2ae895
Name
Last commit
Last update
..
.gitignore Loading commit data...
Makefile.am Loading commit data...
compute-svg-viewbox.c Loading commit data...
defcheck.py Loading commit data...
extract-vector-icon.sh Loading commit data...
generate-news Loading commit data...
gimp-debug-resume.c Loading commit data...
gimp-debug-tool.c Loading commit data...
gimp-mkenums Loading commit data...
gimppath2svg.py Loading commit data...
gimptool.c Loading commit data...
invert-svg.c Loading commit data...
kernelgen.c Loading commit data...
module-dependencies.py Loading commit data...
test-clipboard.c Loading commit data...