(I forgot to switch to my subscribed email address when sending this message so hopefully there isn't a duplicate message later if a moderator passes it)
I'm curious how other people attach a debugger to E17. Currently I've made a X11 session which looks like this. Eterm -e startx -- :1 & sleep 6 Eterm -e gdb /usr/local/bin/enlightenment_e17 `ps -C enlightenment_e17 -o pid=` & enlightenment (Note: I have --program-suffix=_e17 to identify it in the process list from e16) One nuisance is that once gdb attaches it locks E17 and you need to switch to your first display and type continue in the gdb terminal. The other problem is that with Eterm once the command is finished executing the terminal closes. So if there was any debug information you wanted from a clean closing session it'd be gone. This could be fixed by sending the output to a file, but it'd be nice if the terminal didn't close after the command. (Maybe other terminals behave differently but I haven't checked) One other issue is that restarting E will lose gdb and lock E. You have to quit your gdb session for E to be able to restart and then reattach a new gdb. I've looked at the gdb man page and couldn't find a way to automatically continue after attaching. I'm curious if there are options I'm missing or another way of doing this. Do any of you use a debugger other than gdb that is nicer to the program it is debugging? -Arlo ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
