August 2011 - Dillo-dev - lists.mailman3.com

valgrind still unhappy despite expect changes

by corvid＠lavabit.com

Jorge wrote: > On Tue, Aug 30, 2011 at 06:19:38PM +0100, Jeremy Henty wrote: > > > > Jorge Arellano Cid wrote: > > > > > On Tue, Aug 30, 2011 at 12:34:59AM +0100, Jeremy Henty wrote: > > > > > > > > I compile Dillo with 'configure "CFLAGS=-g -O0" "CXXFLAGS= -g > > > > -O0"' to minimise false positives from gcc optimization. > > > > > > Ack. > > > > > > Given you got the log. Do you have a way to reproduce it, or at > > > least have a memory of what you were doing? > > > > Unfortunately no. I automatically run dillo inside valgrind and log > > the output. A cron job reads the logs and updates the reports. These > > days I rarely even look at the logs unless something in the mailing > > list prompts me to. > > > > I am wondering how to add debugging information that could help tie > > valgrind reports to Dillo's actions. Perhaps the CCC could log which > > of its chains is active and which URL it was serving? Then if dlib > > logged its allocations and frees maybe we could identify the URL that > > was responsible? > > Even having the URL wouldn't help much in this case because we > need to know which "cancel" action triggered the last call to > a_Nav_cancel_expect_if_eq(). This would require logging user > actions. > > OTOH, trying to re-build a user action pattern from the CCC > logs would be almost impossible for a human brain (if possible at > all). ;) > > More technically: > > Each bw has its own nav_expect_url; a private copy of a > DilloUrl. Valgrind complains about nav_expect_url, not the bw. So > I wonder how can the bw be valid and not the nav_expect_url, > which is either NULL or a private copy of a DilloUrl? In this one http://starurchin.org/dillo/valgrind/7ea9fc809376ddf7dde2908e2ecf999aea2741… at least, it looks pretty clear that the bw is gone.

Aug. 31, 2011

valgrind still unhappy despite expect changes

by jcid＠dillo.org

On Tue, Aug 30, 2011 at 06:19:38PM +0100, Jeremy Henty wrote: > > Jorge Arellano Cid wrote: > > > On Tue, Aug 30, 2011 at 12:34:59AM +0100, Jeremy Henty wrote: > > > > > > I compile Dillo with 'configure "CFLAGS=-g -O0" "CXXFLAGS= -g > > > -O0"' to minimise false positives from gcc optimization. > > > > Ack. > > > > Given you got the log. Do you have a way to reproduce it, or at > > least have a memory of what you were doing? > > Unfortunately no. I automatically run dillo inside valgrind and log > the output. A cron job reads the logs and updates the reports. These > days I rarely even look at the logs unless something in the mailing > list prompts me to. > > I am wondering how to add debugging information that could help tie > valgrind reports to Dillo's actions. Perhaps the CCC could log which > of its chains is active and which URL it was serving? Then if dlib > logged its allocations and frees maybe we could identify the URL that > was responsible? Even having the URL wouldn't help much in this case because we need to know which "cancel" action triggered the last call to a_Nav_cancel_expect_if_eq(). This would require logging user actions. OTOH, trying to re-build a user action pattern from the CCC logs would be almost impossible for a human brain (if possible at all). ;) More technically: Each bw has its own nav_expect_url; a private copy of a DilloUrl. Valgrind complains about nav_expect_url, not the bw. So I wonder how can the bw be valid and not the nav_expect_url, which is either NULL or a private copy of a DilloUrl? -- Cheers Jorge.-

Aug. 31, 2011

dillo-3.0-rc2 is out

by corvid＠lavabit.com

higuita wrote: > Compiles on slackware64 without problem, but... > > > [ok] resize problems when tabs overflow > > open new tabs takes longer and there is a longer pause > until i can open one more... also, close a tab is also slower. Interesting. Do you know how to use gprof?

Aug. 30, 2011

dillo-3.0-rc2 is out

by higuita7＠yahoo.co.uk

Hi Compiles on slackware64 without problem, but... > [ok] resize problems when tabs overflow open new tabs takes longer and there is a longer pause until i can open one more... also, close a tab is also slower. I also found that slashdot was removed from the default page... any special reason? i use it alot :) thanks higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

Aug. 30, 2011

dillo-3.0-rc2 is out

by jcid＠dillo.org

On Tue, Aug 30, 2011 at 05:47:36PM +0000, corvid wrote: > > We'll need to make a point of mentioning -- at least in the release > announcement, and maybe in README -- how specifying fonts is a little > trickier now with fltk-1.3. OK. Please go ahead and write some directions. It looks like dillorc and the README file are the best places for it. > I wouldn't be surprised if we end up having to try to get fltk to > add another interface of some sort so that those of us who care about > fonts and have a lot of them (i.e., not me) can have font-family work > more consistently. Ack. -- Cheers Jorge.-

Aug. 30, 2011

dillo-3.0-rc2 is out

by corvid＠lavabit.com

We'll need to make a point of mentioning -- at least in the release announcement, and maybe in README -- how specifying fonts is a little trickier now with fltk-1.3. I wouldn't be surprised if we end up having to try to get fltk to add another interface of some sort so that those of us who care about fonts and have a lot of them (i.e., not me) can have font-family work more consistently.

Aug. 30, 2011

valgrind still unhappy despite expect changes

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > On Tue, Aug 30, 2011 at 12:34:59AM +0100, Jeremy Henty wrote: > > > > I compile Dillo with 'configure "CFLAGS=-g -O0" "CXXFLAGS= -g > > -O0"' to minimise false positives from gcc optimization. > > Ack. > > Given you got the log. Do you have a way to reproduce it, or at > least have a memory of what you were doing? Unfortunately no. I automatically run dillo inside valgrind and log the output. A cron job reads the logs and updates the reports. These days I rarely even look at the logs unless something in the mailing list prompts me to. I am wondering how to add debugging information that could help tie valgrind reports to Dillo's actions. Perhaps the CCC could log which of its chains is active and which URL it was serving? Then if dlib logged its allocations and frees maybe we could identify the URL that was responsible? Regards, Jeremy Henty

Aug. 30, 2011

dillo-3.0-rc2 is out

by jcid＠dillo.org

On Tue, Aug 30, 2011 at 12:01:41AM +0200, Axel Beckert wrote: > Hi, > > On Mon, Aug 29, 2011 at 05:07:39PM -0300, Jorge Arellano Cid wrote: > > Today the rc2 was packaged. Please get it here: > > > > http://dillo.org/download/dillo-3.0-pre.tar.bz2 // tarball > > Hrm, the tar ball doesn't contain the autogen.sh script I used for the > Debian packaging. (I build the last two package against the hg > checkout. Not sure if was in earlier dillo packages, i.e. 0.8.6 or so) > Is that file not included on purpose? Yes, autogen.sh uses auto* tools to rebuild the configure script, but the configure script is included in the tarball. It is not in the repository because different auto*tools in different platforms generate slightly different configure scripts leading to almost one configure update per commit... > At least in the README, the instructions still say: > > tar jxvf dillo-3.0.tar.bz2 > cd dillo-3.0 > ./autogen.sh; ./configure; make > sudo make install-strip > > OTOH the INSTALL document skips that step, but AFAICS it never has > been changed since the import into the Mercurial repository while the > README has changed a lot in the "Minor changes for dillo-3.0-rc2" > commit. > > Looks inconsistent to me. Not sure which variant is the intended one. Right. Fixed in the repo to read: tar jxvf dillo-3.0.tar.bz2 cd dillo-3.0 ./configure; make sudo make install-strip -- Cheers Jorge.-

Aug. 30, 2011

valgrind still unhappy despite expect changes

by jcid＠dillo.org

Hi Jeremy, Good to see you in this thread! On Tue, Aug 30, 2011 at 12:34:59AM +0100, Jeremy Henty wrote: > Jorge Arellano Cid wrote: > > > OTOH, valgrind produces some false positives (its docs say it) and > > gcc optimization can also play a role... > > I compile Dillo with 'configure "CFLAGS=-g -O0" "CXXFLAGS= -g -O0"' to > minimise false positives from gcc optimization. Ack. Given you got the log. Do you have a way to reproduce it, or at least have a memory of what you were doing? -- Cheers Jorge.-

Aug. 30, 2011

valgrind still unhappy despite expect changes

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > OTOH, valgrind produces some false positives (its docs say it) and > gcc optimization can also play a role... I compile Dillo with 'configure "CFLAGS=-g -O0" "CXXFLAGS= -g -O0"' to minimise false positives from gcc optimization. Regards, Jeremy Henty

Aug. 30, 2011