- Dillo-dev - lists.mailman3.com

Check out my photos on Facebook

by invite+kr4m2brgrxkx＠facebookmail.com

Hi Dillo-dev, I set up a Facebook profile where I can post my pictures, videos and events and I want to add you as a friend so you can see it. First, you need to join Facebook! Once you join, you can also create your own profile. Thanks, Alan To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=688197402&k=4WM4PYS2WT6G6BDARF43PTPSQ6BAXTZ… Already have an account? Add this email address to your account: http://www.facebook.com/n/?merge_accounts.php&e=dillo-dev%40dillo.org&c=077… ======================================= dillo-dev(a)dillo.org was invited to join Facebook by Alan Carvalho. If you do not wish to receive this type of email from Facebook in the future, please click on the link below to unsubscribe. http://www.facebook.com/o.php?k=66677e&u=100001342010102&mid=2ae4fecG5af360… Facebook, Inc. P.O. Box 10005, Palo Alto, CA 94303

July 19, 2010

[patch]: fix VPATH builds

by onepoint＠starurchin.org

OK, the problem with VPATH builds is fixed but I think it can be improved. Firstly, because -I is a preprocessor directive, it should be added to AM_CPP_FLAGS. Secondly, the Makefile uses .. in various places to navigate from the current build directory to where various headers and libraries are. I think it is better to locate other directories from the top of the build and source trees. So I would prefer to use -I$(top_srcdir) instead of -I$(srcdir)/.. , and $(top_builddir)/path/to/lib instead of ../path/to/lib . Patches attached, tested as before with in-source and external builds. Regards, Jeremy Henty

July 18, 2010

[patch]: fix VPATH builds

by jcid＠dillo.org

On Sat, Jul 17, 2010 at 08:56:06PM +0100, Jeremy Henty wrote: > On Sat, Jul 17, 2010 at 10:19:53AM -0400, Jorge Arellano Cid wrote: > > On Sat, Jul 17, 2010 at 01:11:13PM +0100, Jeremy Henty wrote: > > > > > > The right thing to do is add -I$(srcdir)/.. . Patch attached > > > > Committed. > > Strange! I carefully prepared the patch with tabs for indentation to > be consistent with the rest of the file, yet they have mysteriously > transmuted into 7 spaces! Assuming this was not intentional: > whitespace fixup patch attached. (Handle with care: it appears to do > nothing and if you save it in a way that converts tabs to spaces it > *will* do nothing!) My fault, after copy&paste. Fixed. (good to know it worked with spaces too). -- Cheers Jorge.-

July 17, 2010

[patch]: fix VPATH builds

by onepoint＠starurchin.org

On Sat, Jul 17, 2010 at 10:19:53AM -0400, Jorge Arellano Cid wrote: > On Sat, Jul 17, 2010 at 01:11:13PM +0100, Jeremy Henty wrote: > > > > The right thing to do is add -I$(srcdir)/.. . Patch attached > > Committed. Strange! I carefully prepared the patch with tabs for indentation to be consistent with the rest of the file, yet they have mysteriously transmuted into 7 spaces! Assuming this was not intentional: whitespace fixup patch attached. (Handle with care: it appears to do nothing and if you save it in a way that converts tabs to spaces it *will* do nothing!) Regards, Jeremy Henty

July 17, 2010

[patch]: fix VPATH builds

by jcid＠dillo.org

On Sat, Jul 17, 2010 at 01:11:13PM +0100, Jeremy Henty wrote: > > Currently src/Makefile.am adds -I.. to some compile flags so that all > the #include statements work. This breaks when the build directory is > different from the source directory. The right thing to do is add > -I$(srcdir)/.. . Patch attached (with an extra tidy-up patch as a > bonus). > > Tested both when building in the source directory and outside it. > > Regards, > > Jeremy Henty Committed. -- Cheers Jorge.-

July 17, 2010

[patch]: fix VPATH builds

by onepoint＠starurchin.org

Currently src/Makefile.am adds -I.. to some compile flags so that all the #include statements work. This breaks when the build directory is different from the source directory. The right thing to do is add -I$(srcdir)/.. . Patch attached (with an extra tidy-up patch as a bonus). Tested both when building in the source directory and outside it. Regards, Jeremy Henty

July 17, 2010

Strange dillo2 problems

by jcid＠dillo.org

On Fri, Jul 09, 2010 at 05:32:47PM +0000, corvid wrote: > Simon wrote: > > #4 0x0805e27d in a_Decode_process (dc=0x81ce8d0, instr=0xb7d4a948 "", > > inlen=-1210799800) at decode.c:298 > > > [New Thread -1219286096 (LWP 26986)] > > These strange values leap out at me. > > If you know gdb decently well, tracing through a_Cache_process_dbuf() to > see how it came up with that crazy length would be interesting. This also shows memory was already corrupted before the call: > > #7 0x0805a055 in a_Dialog_save_file ( > > msg=0xfffffdfe <Address 0xfffffdfe out of bounds>, > > pattern=0xfffffdfe <Address 0xfffffdfe out of bounds>, > > fname=0xfffffdfe <Address 0xfffffdfe out of bounds>) at > > dialog.cc:86 -- Cheers Jorge.-

July 9, 2010

Strange dillo2 problems

by corvid＠lavabit.com

Simon wrote: > #4 0x0805e27d in a_Decode_process (dc=0x81ce8d0, instr=0xb7d4a948 "", > inlen=-1210799800) at decode.c:298 > [New Thread -1219286096 (LWP 26986)] These strange values leap out at me. If you know gdb decently well, tracing through a_Cache_process_dbuf() to see how it came up with that crazy length would be interesting.

July 9, 2010

Strange dillo2 problems

by simon.addareyss＠libertysurf.fr

Hello, I'm trying to post a message to the list, but I'm being rejected as a spammer, so I'm trying the "attachment method" :-) Thanks, S.

July 9, 2010

Re: dillo mysteriously freezes

by dennisn＠dennisn.dyndns.org

On Tue, 6 Jul 2010 09:47:19 -0400, Jorge Arellano Cid wrote: > On Tue, Jul 06, 2010 at 03:19:57AM +0000, corvid wrote: > > Dennis wrote: > > > You're right. About everything :). The freezes don't happen with > > > 2.0. I miss the good blazing-fast old days, sometimes. They also > > > don't seem to happen after I downgraded my kernel from 2.6.35-rc3 > > > to 2.6.34. (Although now I have other networking problems -- > > > nfs/scp/etc stalls :S). > > > > I wonder whether there's any connection with > > http://kerneltrap.org/mailarchive/linux-kernel/2010/6/14/4582843/thread > > Exact match! (I wonder how you found it) > > There's even a one-liner patch for the problem in the thread: > http://lkml.org/lkml/2010/6/13/155 > > Have you tried it Dennis? It seems to have worked!! Joy!

July 7, 2010