Hello, guys!
Sorry, I know i´m crossing the borders of off-topic. But I had to tell
you that I could get rid of SEGFAULTs by using a GPtrArray* as member of
my structure. As said before, this struct member shall hold one or more
strings. (John, I have tried using a GList as this
Hi,
First of all, this should really be better documented elsewhere, but
valgrind has some problems debugging and profiling multithreaded code
(such as Gtk/Glib). To get some more accurate results, try the
following:
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --show-reachable myapp
On Tue, 15 Aug 2006 00:57:06 -0300
Fabricio Rocha [EMAIL PROTECTED] wrote:
I have a suspicion from my lack of practice in C: a module of
my program uses a structured type which must contain, as its last
member, a dynamic list of strings, i.e., pointers to gchars (**list).
Sometimes I
On Tue, Aug 15, 2006 at 12:57:06AM -0300, Fabricio Rocha wrote:
Thank you very much, Yeti and Samuel, for your replies!
[...]
I have a suspicion from my lack of practice in C: a module of my
program uses a structured type which must contain, as its last member, a
dynamic list of
Folks,
There is an application which pops up a dialog, fills its widgets, etc
(no user input until now). I usually can exit the program normally
(already implemented a really quit? dialog and such).
However, suddenly (without updating anything in the system) the program
On Fri, Aug 11, 2006 at 12:53:50PM -0300, Fabricio Rocha wrote:
QUESTION: This is quite mysterious for me. If the program runs fine a
lot of times, it does not look a bug in the code itself.
Most likely it is either a race condition or a use of an
undefined value in the code itself.
