On Mon, 26 Dec 2011 12:22:43 +0900 Carsten Haitzler (The Rasterman) <[email protected]> said:
> On Sun, 25 Dec 2011 17:49:21 +0100 Leif Middelschulte > <[email protected]> said: > > > >> On Dec 23, 2011, at 9:41 PM, Carsten Haitzler (The Rasterman) wrote: > > >> > > >> you're going to need to start an xserver raw without any "gdm". > > >> > > >> Xorg -ac :1 & > > >> > > >> run that in a text console somewhere. > > >> in another text console do: > > >> > > >> export E_START=1 > > >> gdb enlightenment > > Thanks to raster for helping out here :-) > > But shouldn't this be > > gdb enlightenment_start instead? > > nup. because enlightenment_start execs enlightenment after some very basic > initial sanity checks/setup. enlightenment_start was intended to not use any > efl (though it now uses eina) so it can set up ld_library_path and other > things in case efl is installed in a non-standard place etc. as such we can > probably kill enlightenment_start now. anyway - an exec breaks gdb's > attachment and then it is no longer tracing e. :) actually i'll correct myself.. we still need enlightenment_start for dbus-launch :) may as well keep it. :) when debugging (launching e under valgrind or gdb) u want to bypass enlightenment_start -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
