[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gcmd-dev] forward bug reports to devel list ?

From: koos
Subject: Re: [gcmd-dev] forward bug reports to devel list ?
Date: Mon, 26 Nov 2007 17:56:51 +0100

Hello Piotr,

I'm getting the impression that glib is to blame for the regex-crash.
When looking at backtraces it is possible to see which functions have
been called successively. 
When examining the backtrace from the regex-crash, the place in the
code which causes the crash is preceeded by a call from the file
libgobject-2.0.so.0. So I don't think gnome-commander is to blame for
Apart from this I can't find any leads, as in other crashes, to find
the problem.


On Sun, 11 Nov 2007 00:00:50 +0100
Piotr Eljasiak <address@hidden> wrote:

> > The backtrace file of the regex crash leads to the file
> > gnome-cmd-string-dialog.c. Unfortunately I cannot use the TRACE
> > macro in this file. In order to use that macro one have to include
> > utils.h, after including that file a lot of error messages appear
> > and compilation fails. I think this is because
> > 'gnome-cmd-string-dialog.c' is still a C source code file and not
> > C++. Do you have any idea what to do?
> > 
> > koos
> Yep, TRACE() macro works for C++ files only. As a workaround you can
> use in c file the following macro:
> #define TRACE(s,fmt)  g_warning (__FILE__ "(%i) %s\t" #s ": `" fmt
> "'", __LINE__, __PRETTY_FUNCTION__, s)
> It should be used in the printf-like way:
> TRACE(string,"%s");
> or
> TRACE(pointer,"%p");
> Hope it'll help,
> Piotr
> _______________________________________________
> gcmd-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/gcmd-devel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]