Having diferent threads making logging could trigger this? or is it
only triggered with g_debug("Somethig recursive: %s",rec(z)) where
rec(z) is something that has a debug inside?
On 2/9/07, Mariano Suárez-Alvarez <msuarezalvarez@xxxxxxxxxxxx> wrote:
> On Fri, 2007-02-09 at 18:15 +0100, José Antonio Sánchez wrote:
> > ---------- Forwarded message ----------
> > From: José Antonio Sánchez <getaceres@xxxxxxxxx>
> > Date: Feb 9, 2007 6:04 PM
> > Subject: Segmentation fault on log
> > To: gtk-app-devel-list@xxxxxxxxx
> >
> >
> > Hello, I'm developing an application using glib's data structures. I
> > also I'm using glib's log capabilities but I'm having a problem.
> > My application dies at one log point and I don't know why. My code is as follow:
> >
> > g_debug("Executing operation %d over %s",op,path);
> >
> > I know that path is not null and that op is a number but I'm getting that error:
> >
> > ** (process:12693): DEBUG (recursed): Executing operation 14 over
> > /home/jasanchez/transfstest/eclipse/plugins/org.eclipse.pde.source_3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG/src/org.eclipse.pde.junit.runtime_3.2.0.v20060605/about.html
> >
> > It applies a lot of operations over a lot of files and the failed file
> > is random but (unless all the othrer debug messages) the last message
> > always starts with ** (process:12693): DEBUG (recursed):
> >
> > What does that recursed mean? I'm sure my application does not call
> > any recursive function in this point. I'm sure is a null pointer
> > dangling and maybe not a problem with glib but I'd like to know what
> > that "recursed" mean in that case.
>
> It means, IIRC, that that message was emitted while processing another
> message.
>
> -- m
>
>
> --
> Mariano Suárez-Alvarez
> http://www.gnome.org/~mariano
>
>
>
--
Saludos.
José Antonio Sánchez
_______________________________________________
gtk-list mailing list
gtk-list@xxxxxxxxx
http://mail.gnome.org/mailman/listinfo/gtk-list
