Re: problem on aborted with core dump

["Donna S. Martin" <donna omartin com>]

I'm not sure precisely what you mean by
"exit the dialog once before I click Bt2..."
If you mean you have to close the dialog,
and bring it back...then can successfully click
Bt2, it sounds like the Bt1 callback is destroying
or changing something set up by your dialog,
something needed by the Bt2 callback. Could
be a logic error, or a coding error (such as
walking in memory).

Best things to do are: be sure you are compiling with
-Wall;  do a trace on your core dump to get a
better grip on what's causing the core; there's
tools like Electric Fence as well...

HTH,
Donna
----- Original Message -----
From: Louis Lu <netlu@visto.com>
To: <gtk-list@gnome.org>
Sent: Thursday, June 08, 2000 7:21 PM
Subject: problem on aborted with core dump


> Hi
>   I wrote a dialog application.  This dialog has
> two buttons (BT1, BT2).  Basically, I click BT1,
> the screen will change its size, and if I click
> BT2, the screen will change its size again.  This
> program is doing many hardware access or (read,
> & write through i2c port to the video and tv chip).
>  However, I could not click BT1, and then click Bt2,
> otherwise I will get core dump.  Meanwhile,
> if I want to click Bt1 and BT2 after, I have to exit
> the dialog once before I click Bt2 in order to avoid
> the core dump.
>
> I hope my description will not confuse you.  I would like
> to know what possibility that cause the core dump.  I would
> very appreciate, some one who has any idea, or suggestions.
>
> Thanks a lot.
>
> Louis
>
>
>
___________________________________________________________________________
> Visit http://www.visto.com/info, your free web-based communications
center.
> Visto.com. Life on the Dot.
>
>
> _______________________________________________
> gtk-list mailing list
> gtk-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gtk-list
>