Nathan Ingersoll wrote:
Run the application using gdb. When it crashes enter the bt command and
send us the output. Sometimes it's useful, other times it's not, but at
least it's a starting point.
On 10/20/05, *Anders Trobäck* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi,
My e_util_eapp_edit crashes with segmentation fault (core dumped)!
How do I report this error? I'm new to debuging stuff!
Running on FreeBSD 5.4, cvs i about four hours old.
\\troback
OK, thanks!
Here we go:
---
(gdb) run /tmp/test.eap
Starting program: /usr/devel/enlightenment/current/bin/e_util_eapp_edit
/tmp/test.eap
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 100518)]
0x28097d69 in ewl_check_checked_set (cb=0x2, c=0) at ewl_check.c:76
76 cb->checked = 1;
(gdb) bt
#0 0x28097d69 in ewl_check_checked_set (cb=0x2, c=0) at ewl_check.c:76
#1 0x0804a233 in main (argc=2, argv=0xbfbfeba8) at eapp_edit_main.c:268
(gdb)
---
e_util_eapp_edit crash as soon as I start it, no window at all!
\\troback
--
============================================
Microsoft is not the answer.
Microsoft is the question.
And 'No' is the answer!
--------------------------------------------
http://www.troback.com
-
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
