Skip to content

enhance(x11/gimp): enable libbacktrace#30317

Draft
robertkirkman wants to merge 2 commits into
termux:masterfrom
robertkirkman:gimp-libbacktrace
Draft

enhance(x11/gimp): enable libbacktrace#30317
robertkirkman wants to merge 2 commits into
termux:masterfrom
robertkirkman:gimp-libbacktrace

Conversation

@robertkirkman

Copy link
Copy Markdown
Member

@robertkirkman robertkirkman marked this pull request as draft July 2, 2026 10:35
@robertkirkman

Copy link
Copy Markdown
Member Author

as far as I can tell, it does not really do anything in gimp

@sylirre

sylirre commented Jul 2, 2026

Copy link
Copy Markdown
Member

It doesn't seem to link with libbacktrace at all

@sylirre

sylirre commented Jul 2, 2026

Copy link
Copy Markdown
Member

Dashboard backtraces: no (unsupported platform) - related

I think it doesn't get enabled because host_os.contains('linux') is actually false: Message: Host os: android

@robertkirkman

Copy link
Copy Markdown
Member Author

Thank you, I didn't notice that at all. I will use that information to check this again.

@robertkirkman

robertkirkman commented Jul 5, 2026

Copy link
Copy Markdown
Member Author

Now it looks like this. I think this is different and I don't remember it looking like this previously.

image

I keep forgetting to save it and having to rewrite it every time I test this, so here is the crafted Segmentation fault I created to test this

--- a/app/app.c
+++ b/app/app.c
@@ -304,7 +304,7 @@ app_run (const gchar         *full_prog_name,
     app_abort (no_interface, abort_message);
 
   /*  initialize lowlevel stuff  */
-  gimp_gegl_init (gimp);
+  gimp_gegl_init ((void*)842982498249);
 
   g_signal_connect_after (gimp, "exit",
                           G_CALLBACK (app_exit_after_callback),

@CVFA1 do you like this?

@robertkirkman robertkirkman marked this pull request as ready for review July 5, 2026 12:47
@robertkirkman robertkirkman marked this pull request as draft July 5, 2026 12:52
@robertkirkman

robertkirkman commented Jul 5, 2026

Copy link
Copy Markdown
Member Author

Never mind, I checked again and it looks very much identical as far as I can tell to how it does when not using the newest patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants