Hmm.. is it a particularly large image? Resynthesizer
is unusally heavy in its memory and processor
requirements, and it would appear that the first is
what is causing the problem.
To debug a plug-in, you'll want to use gdb to attach
to it. This generally is done by having the plug-in
wait for a signal, attaching to the pid, setting
whatever breakpoints, and then sending the signal to
the process. Be sure to compile with -g. However, I'd
suggest learning on something other than resyntesizer
since it is a rather complex chunk of code.
I'd agree it seems not to be a library problem. How
much memory do you have availble? What are the image
--- Reiner Miericke <[EMAIL PROTECTED]> wrote:
> Hello all
> I installed the plugin "resynthesizer" successfully.
> Then I tried to delete a small area from an image.
> But independendly from
> image / area the plugin always crashes and I see the
> GLib-ERROR **: could not allocate 436271616 bytes
> (on stdout).
> My environment looks as follows:
> $ gimp --version
> GIMP Version 1.1.24
> $ ldd /usr/lib/gimp/1.1/plug-ins/resynth
> libgimpui-1.1.so.24 =>
> /usr/lib/libgimpui-1.1.so.24 (0x40020000)
> libgimp-1.1.so.24 =>
> /usr/lib/libgimp-1.1.so.24 (0x40046000)
> libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0
> libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0
> libgmodule-1.2.so.0 =>
> /usr/lib/libgmodule-1.2.so.0 (0x401c7000)
> libglib-1.2.so.0 =>
> /usr/lib/libglib-1.2.so.0 (0x401ca000)
> libdl.so.2 => /lib/libdl.so.2 (0x401ef000)
> libXi.so.6 => /usr/X11R6/lib/libXi.so.6
> libXext.so.6 => /usr/X11R6/lib/libXext.so.6
> libX11.so.6 => /usr/X11R6/lib/libX11.so.6
> libm.so.6 => /lib/libm.so.6 (0x402d9000)
> libc.so.6 => /lib/libc.so.6 (0x402f6000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2
> Anywhere in the user mailing list there was a hint
> to install new libraries.
> But as far as I can see, the libraries above are new
> So, what is going wrong?
> Reiner Miericke
> By the way, how do you debug a plugin?
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.