dnrops
/
gimp
mirror of https://github.com/GNOME/gimp.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

devel-docs: edit and rename debugging-tips file. 

Also list it from the devel-docs README.
This commit is contained in:
Jehan 2022-02-13 21:06:43 +01:00
parent 1918736b99
commit f361009783
2 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
devel-docs/README.md
View File

@ -337,6 +337,9 @@ When writing code, any core developer is expected to follow:
[GIMP's developer wiki](https://wiki.gimp.org/index.php/Main_Page) can
also contain various valuable resources.
Finally the [debugging-tips](debugging-tips.md) file contain many very
useful tricks to help you debugging in various common cases.
### Newcomers
If this is your first time contributing to GIMP, you might be interested

11
devel-docs/debugging-tips.txt → devel-docs/debugging-tips.md
View File

@ -7,9 +7,10 @@ newcomers.
The basic thing is to build babl, GEGL and GIMP with `--enable-debug`.
Note that if you also built glib from source with `--enable-debug`,
every GObject destroyed are apparently overwritten with values invalid
as pointers, so dereferencing one after destruction usually leads to a
crash, which is a good way to find some more vicious bugs.
every pointers of destroyed GObject are overwritten with `0xaa` bytes,
so dereferencing one after destruction usually leads to a crash, which
is a good way to find some more vicious bugs. Also it makes pointers of
destroyed data easy to spot.
## Debug logs ##
@ -61,6 +62,10 @@ shortcut, if you first enable with:
See also: https://wiki.gnome.org/Projects/GTK%2B/Inspector
Note also that running GIMP with `GDK_SCALE=2` (or other values) allow
to test the interface in another scaling than your native one. This
settings is also available in the GtkInspector.
## Debugging GEGL code ##
You may encounter this kind of warning upon exiting GIMP: