Alexandre Julliard julliard@winehq.org wrote:
As a person, who have debugged and fixed quite a bit of GDI handle leaks, and who actually have introduced that facility in the first place, I can say, that an ability to see each line of GDI handle table prefixed with 'dump_gdi_objects:', thread id, or whatever doesn't help at all, but an ability to see more information on the screen wihout need to scroll forth and back, an ability to quickly figure out some pattern in that table really does.
I'm sure everybody thinks the traces they are interested in deserve a different format, but that's not possible for obvious reasons. Just learn to use grep and sed.
Unfortunately that's not always possible, for instance the log created by the app in the bug 29894 is more than 6 Gb. And once I see a suspect GDI handle, I want to see where it was created and how used, if that's wrong handle, I'd like to try another one from the same place of the log.