RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Gegl logging statements

This discussion is connected to the gegl-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.
Gegl logging statements Henrik Akesson 11 Mar 14:57
  Gegl logging statements Martin Nordholts 11 Mar 18:21
Henrik Akesson
2009-03-11 14:57:31 UTC (over 15 years ago)

Gegl logging statements

Hi,

I tend to sprinkle the code with logging statements when learning/debugging. glib has the appropriate functionality for managing the logs... Normally the overhead of the logging statements (if turned off) is neglectable.

Should I leave my log statements in my patches (that will be mainly focused on adding comments)?

Example statement:

g_debug ( "{%s:%u} rectangle split to (%ux%u) and (%ux%u)\n", __FILE__, __LINE__, dr->height, dr->width, fragment->height, fragment->width); Output:

** (lt-gegl:13884): DEBUG: {gegl-processor.c:460} rectangle split to (675x496) and (675x256)

Thanks,

Henrik

Martin Nordholts
2009-03-11 18:21:36 UTC (over 15 years ago)

Gegl logging statements

Henrik Akesson wrote:

Should I leave my log statements in my patches (that will be mainly focused on adding comments)?

Hi,

Please leave them in the patches. I've always wanted more debug logging in GEGL and it is easy to later remove the ones that give noticeable performance hits

BR,
Martin