Greetings all, I certainly hate to complain after all the good work has been done in this new version of Dillo. I wont complain, I will ask a question: When I open Dillo up, if I try to open my bookmarks I get a hard lockup and have to 'xkill' dillo. Anytime I try bookmarks after that, things work just fine. It is only the initial time when I open Dillo that I have this issue. Anyone else have this issue? Running Free BSD 5.1-RC Thanks for the good work! -- Pete http://milneweb.com http://nomorevirus.com
Hi,
When I open Dillo up, if I try to open my bookmarks I get a hard lockup and have to 'xkill' dillo. Anytime I try bookmarks after that, things work just fine. It is only the initial time when I open Dillo that I have this issue. Anyone else have this issue?
Yes - sounds very familar. BUT : lately it works here (for both FreeBSD 4.8-STABLE and 5.1-STABLE). There were issues with starting the dipd and/or bookmakrk plugin. Maybe there still is a race-condition. What you see when you start dillo a second time is that the dpi-system is already up and running. How fast is your machine ? And how busy is it ? Cheers Andreas -- **************************** NEW ADDRESS ****************************** Hamburger Sternwarte Universitaet Hamburg Gojenbergsweg 112 Tel. ++49 40 42891 4016 D-21029 Hamburg, Germany Fax. ++49 40 42891 4198
On Thu, Feb 12, 2004 at 05:33:30PM +0100, Andreas Schweitzer wrote:
There were issues with starting the dipd and/or bookmakrk plugin. Maybe there still is a race-condition.
What you see when you start dillo a second time is that the dpi-system is already up and running.
How fast is your machine ? And how busy is it ?
Cheers Andreas
Andreas, It is a Dual 400 with 512 RAM and not busy at all. Thanks, -- Pete http://milneweb.com http://nomorevirus.com
Some more info on the BSD dpid problem: Actually, there is no need for any changes in the dillo sources. The problem comes from dpid beeing linked with the "-pthread" flag, which has strange consequences on the inherited file descriptors. If "-pthread" is used, one cannot close the inherited file descriptors anymore (one gets EBADF). I don't know, if this is a bug or a feature of the BSD thread implementation. To avoid the problem, one can simple link dpid manually without the "-pthread" flag and everything works fine, at least for me. Johannes
On Sat, 14 Feb 2004, Johannes Hofmann wrote:
Some more info on the BSD dpid problem: Actually, there is no need for any changes in the dillo sources. The problem comes from dpid beeing linked with the "-pthread" flag, which has strange consequences on the inherited file descriptors. If "-pthread" is used, one cannot close the inherited file descriptors anymore (one gets EBADF). I don't know, if this is a bug or a feature of the BSD thread implementation.
To avoid the problem, one can simple link dpid manually without the "-pthread" flag and everything works fine, at least for me.
Very interesting. AFAIU gcc has a way to set its behaviour with respect to the -pthread flag; that way it can be properly set for each OS. Now, in my experience BSD developers are very competent with regard to technical issues, so if it was done on purpose there may be good reasons behind. If that's the case (and not a misconfigured gcc), we can add a check in our configure.in. Cheers Jorge.-
participants (4)
-
Andreas Schweitzer -
Johannes Hofmann -
Jorge Arellano Cid -
Pete