Re: [E-devel] White box of death restart (F1) doesn't work again
On Mon, 29 Aug 2011 11:25:54 -0400 Christopher Michael wrote: > On 08/29/2011 11:22 AM, P Purkayastha wrote: > > > > Looks like the e code is gaining sentience and can fix itself ;) > > > > HAHAHAH !! If only that really was the case... ;) Guess you don't need me any more then. lol -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. signature.asc Description: PGP signature -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 08/30/2011 04:09 AM, Cedric BAIL wrote: > On Mon, Aug 29, 2011 at 11:17 PM, Christopher Michael > wrote: >> On 08/29/2011 05:08 PM, Cedric BAIL wrote: >>> On Mon, Aug 29, 2011 at 10:51 PM, Christopher Michael >>> wrote: On 08/29/2011 02:20 PM, Tom Hacohen wrote: > On 29/08/11 19:06, Christopher Michael wrote: >> >> gdb attach >> (gdb) set unwindonsignal on >> (gdb) call eina_stringshare_del(234234) >> >> works in that it makes it possible to debug using gdb like you are >> (calling efl functions inside gdb). >> >> As far as the alert dialog working (restart/exit), we know it works >> when >> E receives the signal from modules, etc. The problem you are >> experiencing could be from gdb catching the signals instead of E, or it >> could be due to xcb being threaded...not entirely sure which one, but >> the alert code itself does work. >> >> If you compare the changes to the old alert code and this version, you >> will see that there is not much difference really (aside from xcb doing >> the dialog drawing) so I am not sure that This even worked in the old >> version. If it did work previously, then it could just be the threaded >> nature of xcb which is the problem, but as such there is not much can >> be >> done about that...I can't change xcb's threaded nature ;) >> >> I don't know enough about what gdb is doing wrt signals to dig much >> deeper into this. Do we have any gdb gurus that could help ?? > > Sorry, I was'nt clear: call eina_stringshare_del like you did, *detach > gdb* and then press F1/press the button. And still, it fails... This has > nothing to do with gdb, it just fails, so no need for gdb gurus. > > Please check that out. > > -- > Tom. > Sadly, there is not much I can do here :( I keep trying your method of reproduction, but I cannot get (or see) any meaningful reason why this is failing. The only thing I did see that was curious was: When running like this (using gdb to call efl functions and produce an error), the e_signal functions do get called, which in turn does call e_alert_main (thus the white box), BUT what I see happening is that gdb is intercepting the kill(e_pid, SIGUSR2). This causes major problems !!! as now E itself is stuck in pause thus when e_alert_main tries to send the 'restart' command, E never gets to processes it because it (E) is still stuck in pause because gdb intercepted the sigusr2. I am not sure what (if anything) can be done wrt this. The best advise I can give would be to use the 'set unwindonsignal on' as this allows E to receive the SIGUSR2 and thus continue with the restart. >>> >>> If that's the issue, why don't we simplify the code of e_alert by >>> directly using fork/exec/waitpid and taking the exit code of >>> enlightenment_alert as the order. Exit code of 0 mean exit and 1 >>> restart. That would simplify a lot the code path of both part >>> (something that make sense when you are already in bad shape). >> >> I would not be against that as an option :) It does make more sense. If I >> can find some time soon, I'll go ahead and do that...if not, it may have to >> wait a little while. > > Ok, I just experienced the White Death Box and I confirm it's borken ! > If you don't have the time to fix it, tell me, the code look pretty > simple to do the modification and I can do it quickly as it's a little > bit annoying :-) By all means, feel free to jump in ;) Yes, the code is not that difficult to understand :) dh -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On Mon, Aug 29, 2011 at 11:17 PM, Christopher Michael wrote: > On 08/29/2011 05:08 PM, Cedric BAIL wrote: >> On Mon, Aug 29, 2011 at 10:51 PM, Christopher Michael >> wrote: >>> On 08/29/2011 02:20 PM, Tom Hacohen wrote: On 29/08/11 19:06, Christopher Michael wrote: > > gdb attach > (gdb) set unwindonsignal on > (gdb) call eina_stringshare_del(234234) > > works in that it makes it possible to debug using gdb like you are > (calling efl functions inside gdb). > > As far as the alert dialog working (restart/exit), we know it works > when > E receives the signal from modules, etc. The problem you are > experiencing could be from gdb catching the signals instead of E, or it > could be due to xcb being threaded...not entirely sure which one, but > the alert code itself does work. > > If you compare the changes to the old alert code and this version, you > will see that there is not much difference really (aside from xcb doing > the dialog drawing) so I am not sure that This even worked in the old > version. If it did work previously, then it could just be the threaded > nature of xcb which is the problem, but as such there is not much can > be > done about that...I can't change xcb's threaded nature ;) > > I don't know enough about what gdb is doing wrt signals to dig much > deeper into this. Do we have any gdb gurus that could help ?? Sorry, I was'nt clear: call eina_stringshare_del like you did, *detach gdb* and then press F1/press the button. And still, it fails... This has nothing to do with gdb, it just fails, so no need for gdb gurus. Please check that out. -- Tom. >>> >>> Sadly, there is not much I can do here :( I keep trying your method of >>> reproduction, but I cannot get (or see) any meaningful reason why this >>> is failing. The only thing I did see that was curious was: >>> >>> When running like this (using gdb to call efl functions and produce an >>> error), the e_signal functions do get called, which in turn does call >>> e_alert_main (thus the white box), BUT what I see happening is that gdb >>> is intercepting the kill(e_pid, SIGUSR2). This causes major problems !!! >>> as now E itself is stuck in pause thus when e_alert_main tries to send >>> the 'restart' command, E never gets to processes it because it (E) is >>> still stuck in pause because gdb intercepted the sigusr2. >>> >>> I am not sure what (if anything) can be done wrt this. The best advise I >>> can give would be to use the 'set unwindonsignal on' as this allows E to >>> receive the SIGUSR2 and thus continue with the restart. >> >> If that's the issue, why don't we simplify the code of e_alert by >> directly using fork/exec/waitpid and taking the exit code of >> enlightenment_alert as the order. Exit code of 0 mean exit and 1 >> restart. That would simplify a lot the code path of both part >> (something that make sense when you are already in bad shape). > > I would not be against that as an option :) It does make more sense. If I > can find some time soon, I'll go ahead and do that...if not, it may have to > wait a little while. Ok, I just experienced the White Death Box and I confirm it's borken ! If you don't have the time to fix it, tell me, the code look pretty simple to do the modification and I can do it quickly as it's a little bit annoying :-) -- Cedric BAIL -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 08/29/2011 05:08 PM, Cedric BAIL wrote: > On Mon, Aug 29, 2011 at 10:51 PM, Christopher Michael > wrote: >> On 08/29/2011 02:20 PM, Tom Hacohen wrote: >>> On 29/08/11 19:06, Christopher Michael wrote: gdb attach (gdb) set unwindonsignal on (gdb) call eina_stringshare_del(234234) works in that it makes it possible to debug using gdb like you are (calling efl functions inside gdb). As far as the alert dialog working (restart/exit), we know it works when E receives the signal from modules, etc. The problem you are experiencing could be from gdb catching the signals instead of E, or it could be due to xcb being threaded...not entirely sure which one, but the alert code itself does work. If you compare the changes to the old alert code and this version, you will see that there is not much difference really (aside from xcb doing the dialog drawing) so I am not sure that This even worked in the old version. If it did work previously, then it could just be the threaded nature of xcb which is the problem, but as such there is not much can be done about that...I can't change xcb's threaded nature ;) I don't know enough about what gdb is doing wrt signals to dig much deeper into this. Do we have any gdb gurus that could help ?? >>> >>> Sorry, I was'nt clear: call eina_stringshare_del like you did, *detach >>> gdb* and then press F1/press the button. And still, it fails... This has >>> nothing to do with gdb, it just fails, so no need for gdb gurus. >>> >>> Please check that out. >>> >>> -- >>> Tom. >>> >> >> Sadly, there is not much I can do here :( I keep trying your method of >> reproduction, but I cannot get (or see) any meaningful reason why this >> is failing. The only thing I did see that was curious was: >> >> When running like this (using gdb to call efl functions and produce an >> error), the e_signal functions do get called, which in turn does call >> e_alert_main (thus the white box), BUT what I see happening is that gdb >> is intercepting the kill(e_pid, SIGUSR2). This causes major problems !!! >> as now E itself is stuck in pause thus when e_alert_main tries to send >> the 'restart' command, E never gets to processes it because it (E) is >> still stuck in pause because gdb intercepted the sigusr2. >> >> I am not sure what (if anything) can be done wrt this. The best advise I >> can give would be to use the 'set unwindonsignal on' as this allows E to >> receive the SIGUSR2 and thus continue with the restart. > > If that's the issue, why don't we simplify the code of e_alert by > directly using fork/exec/waitpid and taking the exit code of > enlightenment_alert as the order. Exit code of 0 mean exit and 1 > restart. That would simplify a lot the code path of both part > (something that make sense when you are already in bad shape). I would not be against that as an option :) It does make more sense. If I can find some time soon, I'll go ahead and do that...if not, it may have to wait a little while. dh -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On Mon, Aug 29, 2011 at 10:51 PM, Christopher Michael wrote: > On 08/29/2011 02:20 PM, Tom Hacohen wrote: >> On 29/08/11 19:06, Christopher Michael wrote: >>> gdb attach >>> (gdb) set unwindonsignal on >>> (gdb) call eina_stringshare_del(234234) >>> >>> works in that it makes it possible to debug using gdb like you are >>> (calling efl functions inside gdb). >>> >>> As far as the alert dialog working (restart/exit), we know it works when >>> E receives the signal from modules, etc. The problem you are >>> experiencing could be from gdb catching the signals instead of E, or it >>> could be due to xcb being threaded...not entirely sure which one, but >>> the alert code itself does work. >>> >>> If you compare the changes to the old alert code and this version, you >>> will see that there is not much difference really (aside from xcb doing >>> the dialog drawing) so I am not sure that This even worked in the old >>> version. If it did work previously, then it could just be the threaded >>> nature of xcb which is the problem, but as such there is not much can be >>> done about that...I can't change xcb's threaded nature ;) >>> >>> I don't know enough about what gdb is doing wrt signals to dig much >>> deeper into this. Do we have any gdb gurus that could help ?? >> >> Sorry, I was'nt clear: call eina_stringshare_del like you did, *detach >> gdb* and then press F1/press the button. And still, it fails... This has >> nothing to do with gdb, it just fails, so no need for gdb gurus. >> >> Please check that out. >> >> -- >> Tom. >> > > Sadly, there is not much I can do here :( I keep trying your method of > reproduction, but I cannot get (or see) any meaningful reason why this > is failing. The only thing I did see that was curious was: > > When running like this (using gdb to call efl functions and produce an > error), the e_signal functions do get called, which in turn does call > e_alert_main (thus the white box), BUT what I see happening is that gdb > is intercepting the kill(e_pid, SIGUSR2). This causes major problems !!! > as now E itself is stuck in pause thus when e_alert_main tries to send > the 'restart' command, E never gets to processes it because it (E) is > still stuck in pause because gdb intercepted the sigusr2. > > I am not sure what (if anything) can be done wrt this. The best advise I > can give would be to use the 'set unwindonsignal on' as this allows E to > receive the SIGUSR2 and thus continue with the restart. If that's the issue, why don't we simplify the code of e_alert by directly using fork/exec/waitpid and taking the exit code of enlightenment_alert as the order. Exit code of 0 mean exit and 1 restart. That would simplify a lot the code path of both part (something that make sense when you are already in bad shape). -- Cedric BAIL -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 08/29/2011 02:20 PM, Tom Hacohen wrote: > On 29/08/11 19:06, Christopher Michael wrote: >> gdb attach >> (gdb) set unwindonsignal on >> (gdb) call eina_stringshare_del(234234) >> >> works in that it makes it possible to debug using gdb like you are >> (calling efl functions inside gdb). >> >> As far as the alert dialog working (restart/exit), we know it works when >> E receives the signal from modules, etc. The problem you are >> experiencing could be from gdb catching the signals instead of E, or it >> could be due to xcb being threaded...not entirely sure which one, but >> the alert code itself does work. >> >> If you compare the changes to the old alert code and this version, you >> will see that there is not much difference really (aside from xcb doing >> the dialog drawing) so I am not sure that This even worked in the old >> version. If it did work previously, then it could just be the threaded >> nature of xcb which is the problem, but as such there is not much can be >> done about that...I can't change xcb's threaded nature ;) >> >> I don't know enough about what gdb is doing wrt signals to dig much >> deeper into this. Do we have any gdb gurus that could help ?? > > Sorry, I was'nt clear: call eina_stringshare_del like you did, *detach > gdb* and then press F1/press the button. And still, it fails... This has > nothing to do with gdb, it just fails, so no need for gdb gurus. > > Please check that out. > > -- > Tom. > Sadly, there is not much I can do here :( I keep trying your method of reproduction, but I cannot get (or see) any meaningful reason why this is failing. The only thing I did see that was curious was: When running like this (using gdb to call efl functions and produce an error), the e_signal functions do get called, which in turn does call e_alert_main (thus the white box), BUT what I see happening is that gdb is intercepting the kill(e_pid, SIGUSR2). This causes major problems !!! as now E itself is stuck in pause thus when e_alert_main tries to send the 'restart' command, E never gets to processes it because it (E) is still stuck in pause because gdb intercepted the sigusr2. I am not sure what (if anything) can be done wrt this. The best advise I can give would be to use the 'set unwindonsignal on' as this allows E to receive the SIGUSR2 and thus continue with the restart. dh -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 29/08/11 19:06, Christopher Michael wrote: > gdb attach > (gdb) set unwindonsignal on > (gdb) call eina_stringshare_del(234234) > > works in that it makes it possible to debug using gdb like you are > (calling efl functions inside gdb). > > As far as the alert dialog working (restart/exit), we know it works when > E receives the signal from modules, etc. The problem you are > experiencing could be from gdb catching the signals instead of E, or it > could be due to xcb being threaded...not entirely sure which one, but > the alert code itself does work. > > If you compare the changes to the old alert code and this version, you > will see that there is not much difference really (aside from xcb doing > the dialog drawing) so I am not sure that This even worked in the old > version. If it did work previously, then it could just be the threaded > nature of xcb which is the problem, but as such there is not much can be > done about that...I can't change xcb's threaded nature ;) > > I don't know enough about what gdb is doing wrt signals to dig much > deeper into this. Do we have any gdb gurus that could help ?? Sorry, I was'nt clear: call eina_stringshare_del like you did, *detach gdb* and then press F1/press the button. And still, it fails... This has nothing to do with gdb, it just fails, so no need for gdb gurus. Please check that out. -- Tom. -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 08/29/2011 11:20 AM, Tom Hacohen wrote: > On 29/08/11 18:06, Christopher Michael wrote: >> Ok, well I am just getting caught up due to the storm, but I'll look @ >> this today and run some tests. Just out of curiosity, if you send E a >> segv (kill -s SEGV ) like Sachiel suggested when we had this >> problem before, does the Restart work ? >> >> dh >> >> > > Oddly enough, sending a SEGV from outside the process works just fine. > But attaching gdb to the e process, and then doing something like: > eina_stringshare_del(2342344234) from inside gdb breaks as expected. > > -- > Tom. > Tom, gdb attach (gdb) set unwindonsignal on (gdb) call eina_stringshare_del(234234) works in that it makes it possible to debug using gdb like you are (calling efl functions inside gdb). As far as the alert dialog working (restart/exit), we know it works when E receives the signal from modules, etc. The problem you are experiencing could be from gdb catching the signals instead of E, or it could be due to xcb being threaded...not entirely sure which one, but the alert code itself does work. If you compare the changes to the old alert code and this version, you will see that there is not much difference really (aside from xcb doing the dialog drawing) so I am not sure that This even worked in the old version. If it did work previously, then it could just be the threaded nature of xcb which is the problem, but as such there is not much can be done about that...I can't change xcb's threaded nature ;) I don't know enough about what gdb is doing wrt signals to dig much deeper into this. Do we have any gdb gurus that could help ?? dh -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 08/29/2011 11:22 AM, P Purkayastha wrote: > > On Monday, August 29, 2011 11:06:13 PM UTC+8, Christopher Michael wrote: >> >> On 08/29/2011 10:51 AM, Tom Hacohen wrote: >>> On 29/08/11 17:40, Christopher Michael wrote: Uggg, WTH !! How can this be broken again ? :( Tom, I assume you are still building evas/ecore w/ Xlib support ? What exactly is broken ? The box doesn't show anymore ? Restart doesn't work with the mouse? keyboard ? Exit is broken ?? Need more details mate ;) >>> >>> Yeah, I'm still an xlib coward (btw, glima suffers from the same issue). >>> >>> So evas/ecore w/ Xlib. >>> >>> Broken: restart just exits e, either cause of a seg or I dunno what. >>> I didn't provide any info because it's the same issue as before. >>> >>> -- >>> Tom. >>> >> >> Ok, well I am just getting caught up due to the storm, but I'll look @ >> this today and run some tests. Just out of curiosity, if you send E a >> segv (kill -s SEGV) like Sachiel suggested when we had this >> problem before, does the Restart work ? >> >> dh >> > > Uh. Can't repro this today using > kill -s SEGV $(pgrep -x enlightenment) > > Running 62899. But, F1 was definitely a problem 2 days ago. It was behaving > the same as F2. Anyway, hopefully it fixed itself :P > > Looks like the e code is gaining sentience and can fix itself ;) > HAHAHAH !! If only that really was the case... ;) dh -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 08/29/2011 11:20 AM, Tom Hacohen wrote: > On 29/08/11 18:06, Christopher Michael wrote: >> Ok, well I am just getting caught up due to the storm, but I'll look @ >> this today and run some tests. Just out of curiosity, if you send E a >> segv (kill -s SEGV ) like Sachiel suggested when we had this >> problem before, does the Restart work ? >> >> dh >> >> > > Oddly enough, sending a SEGV from outside the process works just fine. Ok, great. Then the alert code is working as expected. > But attaching gdb to the e process, and then doing something like: > eina_stringshare_del(2342344234) from inside gdb breaks as expected. > > -- > Tom. > Hmm, odd since it works as per above, but ok. At least this gives me something to work with and dig into ;) dh -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On Monday, August 29, 2011 11:06:13 PM UTC+8, Christopher Michael wrote: > > On 08/29/2011 10:51 AM, Tom Hacohen wrote: > > On 29/08/11 17:40, Christopher Michael wrote: > >> Uggg, WTH !! How can this be broken again ? :( > >> > >> Tom, > >> > >> I assume you are still building evas/ecore w/ Xlib support ? > >> What exactly is broken ? The box doesn't show anymore ? Restart doesn't > >> work with the mouse? keyboard ? Exit is broken ?? > >> > >> Need more details mate ;) > > > > Yeah, I'm still an xlib coward (btw, glima suffers from the same issue). > > > > So evas/ecore w/ Xlib. > > > > Broken: restart just exits e, either cause of a seg or I dunno what. > > I didn't provide any info because it's the same issue as before. > > > > -- > > Tom. > > > > Ok, well I am just getting caught up due to the storm, but I'll look @ > this today and run some tests. Just out of curiosity, if you send E a > segv (kill -s SEGV ) like Sachiel suggested when we had this > problem before, does the Restart work ? > > dh > Uh. Can't repro this today using kill -s SEGV $(pgrep -x enlightenment) Running 62899. But, F1 was definitely a problem 2 days ago. It was behaving the same as F2. Anyway, hopefully it fixed itself :P Looks like the e code is gaining sentience and can fix itself ;) -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 29/08/11 18:06, Christopher Michael wrote: > Ok, well I am just getting caught up due to the storm, but I'll look @ > this today and run some tests. Just out of curiosity, if you send E a > segv (kill -s SEGV ) like Sachiel suggested when we had this > problem before, does the Restart work ? > > dh > > Oddly enough, sending a SEGV from outside the process works just fine. But attaching gdb to the e process, and then doing something like: eina_stringshare_del(2342344234) from inside gdb breaks as expected. -- Tom. -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 08/29/2011 10:51 AM, Tom Hacohen wrote: > On 29/08/11 17:40, Christopher Michael wrote: >> Uggg, WTH !! How can this be broken again ? :( >> >> Tom, >> >> I assume you are still building evas/ecore w/ Xlib support ? >> What exactly is broken ? The box doesn't show anymore ? Restart doesn't >> work with the mouse? keyboard ? Exit is broken ?? >> >> Need more details mate ;) > > Yeah, I'm still an xlib coward (btw, glima suffers from the same issue). > > So evas/ecore w/ Xlib. > > Broken: restart just exits e, either cause of a seg or I dunno what. > I didn't provide any info because it's the same issue as before. > > -- > Tom. > Ok, well I am just getting caught up due to the storm, but I'll look @ this today and run some tests. Just out of curiosity, if you send E a segv (kill -s SEGV ) like Sachiel suggested when we had this problem before, does the Restart work ? dh -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 29/08/11 17:40, Christopher Michael wrote: > Uggg, WTH !! How can this be broken again ? :( > > Tom, > > I assume you are still building evas/ecore w/ Xlib support ? > What exactly is broken ? The box doesn't show anymore ? Restart doesn't > work with the mouse? keyboard ? Exit is broken ?? > > Need more details mate ;) Yeah, I'm still an xlib coward (btw, glima suffers from the same issue). So evas/ecore w/ Xlib. Broken: restart just exits e, either cause of a seg or I dunno what. I didn't provide any info because it's the same issue as before. -- Tom. -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] White box of death restart (F1) doesn't work again
On 08/29/2011 02:55 AM, Tom Hacohen wrote: > Hey everyone (dh?), > > This is broken again. And since this is the #1 feature I care about, I'm > sad. :( > > Whoever broke it, please fix it. > > Thanks, > Tom. > Uggg, WTH !! How can this be broken again ? :( Tom, I assume you are still building evas/ecore w/ Xlib support ? What exactly is broken ? The box doesn't show anymore ? Restart doesn't work with the mouse? keyboard ? Exit is broken ?? Need more details mate ;) dh -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] White box of death restart (F1) doesn't work again
Hey everyone (dh?), This is broken again. And since this is the #1 feature I care about, I'm sad. :( Whoever broke it, please fix it. Thanks, Tom. -- EMC VNX: the world's simplest storage, starting under $10K The only unified storage solution that offers unified management Up to 160% more powerful than alternatives and 25% more efficient. Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
