On Mon, 29 Aug 2005 16:13:41 +0000 Fernando Meira <[EMAIL PROTECTED]> babbled:

> Hi,
> 
> been trying to make the necessary changes to compile e and e_modules with 
> debug flags, by following your suggestion of creating an alias. That all I 
> did, but I think it didn't work.. at least, I still have the same (or very 
> similar) output from gdb:

rebuild ecore, edje, evas, eet and embryo with debug (-g) CFLAGS as well.

> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 9038)]
> 0xb759ecd8 in ?? ()
> (gdb) bt
> #0 0xb759ecd8 in ?? ()
> #1 0xb7b5f24e in _ecore_event_call () from /usr/lib/libecore.so.1
> #2 0x43134edc in ?? ()
> #3 0x0008d549 in ?? ()
> #4 0x00000003 in ?? ()
> #5 0xb7b6711c in ?? () from /usr/lib/libecore.so.1
> #6 0x00000000 in ?? ()
> #7 0x00000000 in ?? ()
> #8 0x00000001 in ?? ()
> #9 0xb7b629b4 in _ecore_main_shutdown () from /usr/lib/libecore.so.1
> #10 0x00000001 in ?? ()
> #11 0x00000000 in ?? ()
> #12 0xb7250991 in ?? ()
> #13 0x41d0c4d3 in ?? ()
> #14 0xd4000000 in ?? ()
> #15 0x3f93f398 in ?? ()
> #16 0xb7b5ba5c in ?? () from /usr/lib/libecore.so.1
> #17 0x00000000 in ?? ()
> #18 0xb7b62806 in _ecore_main_shutdown () from /usr/lib/libecore.so.1
> #19 0xb7f37c80 in ?? () from /lib/ld-linux.so.2
> #20 0xbfb33d18 in ?? ()
> #21 0xb7b62b99 in ecore_main_loop_begin () from /usr/lib/libecore.so.1
> #22 0xb7b62b70 in ecore_main_loop_begin () from /usr/lib/libecore.so.1
> #23 0x0805a259 in main (argc=0, argv=0x4d9) at e_main.c:568
> (gdb) 
> 
> I did not change anything in make.conf (yes I'm using gentoo, how did you 
> both guessed that?), so the -fomit-frame-pointer flag is still there, but 
> from what I understood, using the alias as yours, it would be enough.. is 
> this right? If so, what went wrong? I did re-compile e and e_modules. 
> Embrace module did work better but when I disable it provoked the error 
> message above.
> 
> So, could you give me some more info about what I need to do? 
> Thanks!
> Fernando.
> 
> On 8/28/05, Bertrand Jacquin <[EMAIL PROTECTED]> wrote:
> > 
> > Personaly I have this alias :
> > alias emdebug="CFLAGS=-g FEATURES=nostrip emerge"
> > 
> > so when I want to compile a e stuff, I just do emdebug -va efoo and
> > debugging symbols are safe.
> > 
> > Last months I hack enlightenment.eclass to do that but that's not the
> > job of portage but yours and vapier (e ebuilds maintener refused it
> > also). Also there's no uncrappy solution in portage to do that so
> > upper solution is a KISS.
> > 
> > ++
> > 
> > On 8/28/05, Mathieu <[EMAIL PROTECTED]> wrote:
> > > Fernando Meira <[EMAIL PROTECTED]> disait dernièrement que :
> > >
> > > > On 8/27/05, Mathieu <[EMAIL PROTECTED]> wrote:
> > > >>
> > > >> I hope you have at least e_modules and e compiled with debugging
> > > >> symbols and with no -fomit-frame-pointer option.
> > > >
> > > >
> > > > Oh, forgot to ask:how do I know if I compiled with debugging symbol?
> > > > I did compile with -fomit-frame-pointer option though... should I 
> > recompile
> > > > without that and try again?
> > >
> > > I answer to this mail for both.
> > > As I expected you compiled without debugging stuff and with
> > > -fomit-frame-pointer, so the bt isn't useful :)
> > >
> > > I guess you use Gentoo as a distro.
> > >
> > > First, to have debugging symbols compiled in, you have to pass -g as
> > > option to gcc. frame pointers are necessary to have a debugging
> > > session be useful
> > > In portage, there is a debug.eclass, which for ebuilds inheriting it,
> > > add a USE flag debug, which when activated takes care of stripping
> > > "dangerous-for-debugging" cflags and adding -g to it.
> > > I am gonna file a bug against E17 ebuilds to have it included.
> > >
> > > For my particular case, I copied the enlightenment.eclass file from
> > > regular portage into my overlay
> > > (http://gentoo-wiki.com/Portage_Overlay)
> > > and in the very first lines, I add enlightenment to the line beginning
> > > by "inherits"
> > >
> > > at this time, you can set per package use flags by means of
> > > /etc/portage/package.use (I recommend you read man portage, you will
> > > find many many interesting things, if you haven't yet)
> > > setting the debug flags for a least x11-wm/e and x11-plugins/e_modules
> > > and rebuilding e and e_modules thru emerge would get us a more
> > > explicit report. :)
> > >
> > > --
> > > Mathieu
> > >
> > >
> > > -------------------------------------------------------
> > > SF.Net email is Sponsored by the Better Software Conference & EXPO
> > > September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
> > Practices
> > > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & 
> > QA
> > > Security * Process Improvement & Measurement * 
> > http://www.sqe.com/bsce5sf
> > > _______________________________________________
> > > enlightenment-users mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> > >
> > 
> > 
> > --
> > Beber
> > [EMAIL PROTECTED]
> >
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [EMAIL PROTECTED]
裸好多                              [EMAIL PROTECTED]
Tokyo, Japan (東京 日本)


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to