May 2004 - Dillo-dev - lists.mailman3.com

Re: [Dillo-dev]dillo-0.8.1-pre2.tar.bz2

by Jorge Arellano Cid

Riccardo, > Someone is in the search for good news? I have none. > > > Riccardo Mottola wrote: > > Program received signal SIGILL, Illegal instruction. > > 0x0 in ?? () from /usr/local/build/dillo-0.8.1-pre2/src/dillo > > > > I think this is a GTK related bug. I compiled a small program (gcolor) > that uses gtk and it dies the same way! > I have gtk 1.2.10 patched with Jorge's func_data type patch. > I never used gtk except for dillo... > > Now, maybe I know why the idea of a Motif port or widget independent > port is getting into my head again. Oh the fears of GTK! It's not GTK, but AIX. Just google search for the problem you have. Frankly, you're in the best position to solve it because you have the AIX machine at hand. If you're not a developer, try asking an experienced AIX developer that has had the same problem. As for the testing on Solaris, please send me the machine/OS SPEC to include it in the compatibility list. Cheers Jorge.-

May 10, 2004

Re: [Dillo-dev]dillo-0.8.1-pre2.tar.bz2

by Riccardo Mottola

Someone is in the search for good news? I have none. Riccardo Mottola wrote: > Program received signal SIGILL, Illegal instruction. > 0x0 in ?? () from /usr/local/build/dillo-0.8.1-pre2/src/dillo > I think this is a GTK related bug. I compiled a small program (gcolor) that uses gtk and it dies the same way! I have gtk 1.2.10 patched with Jorge's func_data type patch. I never used gtk except for dillo... Now, maybe I know why the idea of a Motif port or widget independent port is getting into my head again. Oh the fears of GTK! -Riccardo

May 10, 2004

Re: [Dillo-dev]dillo-0.8.1-pre2.tar.bz2

by Riccardo Mottola

Jorge Arellano Cid wrote: > Any use of the browser serves, specially testing the new > download feature and multiple windows at the same time. I have compiled and run pre3 on a Solaris 2.6 sparcstation 32 bit. I browsed around, opened multiple windows and it seems to behave fine. I used this browser test from the iCab people (a light browser for MacOS): http://www.icab.de/test.html and seen that dillo fails quite trhough those tests. The I tried compiling on AIX again, pre2. (gdb) run Starting program: /usr/local/build/dillo-0.8.1-pre2/src/dillo Program received signal SIGILL, Illegal instruction. 0x0 in ?? () from /usr/local/build/dillo-0.8.1-pre2/src/dillo the interesting is that I was working on an exported display, without having set the DISPLAY variable. So X apps couldn't possibly start and should output % xlogo Error: Can't open display: This means dillo si failing really early on AIX. These warnings may not be essential, but they may be worth looking: dpid.c: In function `init_srs_socket': dpid.c:409: warning: implicit declaration of function `bzero' downloads.c:179: warning: implicit declaration of function `bzero' I still get those errors: main.c: In function `start_filter_plugin': main.c:47: warning: passing arg 3 of `naccept' from incompatible pointer type but they shouldn't be fatal, AIX must be pricky about socket types and I get that waring with other programs too. socket.h defines: extern "C" int naccept(int, struct sockaddr *, size_t *); and types.h says: types.h:typedef unsigned long size_t; configure reports checking for gethostbyname... yes checking for setsockopt... yes checking for socklen_t... int Cheers, Riccardo

May 10, 2004

Re: [Dillo-dev]dillo-0.8.1-pre2.tar.bz2

by Riccardo Mottola

Jorge Arellano Cid wrote: > > > Any use of the browser serves, specially testing the new > download feature and multiple windows at the same time. I tested it on OpenBSD/sparc and I browsed all the evening without apparent problems, i didn't stress it further though. tomorrow I will try Solaris again and maybe give AIX a new kick. But AIX is beginning to be a black sheep here :) Maybe I test it on NetBSD/68k too if I can... I'll let you know if any problems appear on some platform -Riccardo

May 9, 2004

Re: [Dillo-dev]dillo-0.8.1-pre2.tar.bz2

by Jorge Arellano Cid

On Sun, 9 May 2004, Johannes Hofmann wrote: > Hi, > > dillo-0.8.1-pre2.tar.bz2 works nice here on DragonFly-BSD. The new > handling of unknown MIME types is really a great addition. Good! > Just one little thing: When canceling from the save dialog, the > stop-button stays clickable. Shouldn't it get greyed out? Yes it should; Fixed and commited. Patch: diff -pru dillo/src/cache.c dillo-0.8.0/src/cache.c --- dillo/src/cache.c 2004-05-08 20:31:37.000000000 -0400 +++ dillo-0.8.0/src/cache.c 2004-05-09 14:24:18.000000000 -0400 @@ -827,6 +827,7 @@ static void Cache_process_queue(CacheDat if (st == -1 && ClientWeb->flags & WEB_RootUrl) { /* Unhandled MIME type, prepare a download offer... */ AbortEntry = TRUE; + a_Interface_remove_client(Client_bw, Client->Key); Cache_client_dequeue(Client, NULLKey); --i; /* Keep the index value in the next iteration */ continue; Cheers Jorge.-

May 9, 2004

Re: [Dillo-dev]dillo-0.8.1-pre2.tar.bz2

by Johannes Hofmann

Hi, dillo-0.8.1-pre2.tar.bz2 works nice here on DragonFly-BSD. The new handling of unknown MIME types is really a great addition. Just one little thing: When canceling from the save dialog, the stop-button stays clickable. Shouldn't it get greyed out? Cheers, Johannes On Sat, May 08, 2004 at 08:29:01PM -0400, Jorge Arellano Cid wrote: > > Hi there! > > It took a long time, but finally, dillo-0.8.1-pre2.tar.bz2 is > ready for download. > > The problem was that the patch for the problem of left-clicking > an unhandled MIME type involved changes, inside the cache module, > that were not trivial. > > I pondered the situation carefully trying to decide whether to > make the patch and delay the next release, or leave it for 0.8.2. > After studying the situation and developing a patch, important > changes were made in the cache (for instance all the cached URLs > use new code now, and the main scheduler was also changed, and > the posibility of deleting an active URL-transfer was made > possible). > > After all that, it only remained to offer a download dialog for > the aborted transfer, and as the patch was already major, I went > ahead and the result was one of those improvements you can't > leave out. > > What does it do? well, now you can left-click on any URL; if it > happens to be of an unhandled MIME type, the transfer is aborted, > and a download dialog appears to offer the possibility of saving > the resource locally. Simple and clean. Now you can click > carelessly on those fake-download links from SF until you reach > the real source ;). > > The tradeoff: the possibility of labelling this release as > "beta stable" is not as clear as before. This tarball requires > plenty of testing, so please download it and give it a hard time! > > Any use of the browser serves, specially testing the new > download feature and multiple windows at the same time. > > Get it from: > > http://www.dillo.org/download/dillo-0.8.1-pre2.tar.bz2 > > and report back to dillo-dev. > > Cheers > Jorge.- > > > PS: Kudos are also welcome! ;) > > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev(a)lists.auriga.wearlab.de > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

May 9, 2004

[Dillo-dev]dillo-0.8.1-pre2.tar.bz2

by Jorge Arellano Cid

Hi there! It took a long time, but finally, dillo-0.8.1-pre2.tar.bz2 is ready for download. The problem was that the patch for the problem of left-clicking an unhandled MIME type involved changes, inside the cache module, that were not trivial. I pondered the situation carefully trying to decide whether to make the patch and delay the next release, or leave it for 0.8.2. After studying the situation and developing a patch, important changes were made in the cache (for instance all the cached URLs use new code now, and the main scheduler was also changed, and the posibility of deleting an active URL-transfer was made possible). After all that, it only remained to offer a download dialog for the aborted transfer, and as the patch was already major, I went ahead and the result was one of those improvements you can't leave out. What does it do? well, now you can left-click on any URL; if it happens to be of an unhandled MIME type, the transfer is aborted, and a download dialog appears to offer the possibility of saving the resource locally. Simple and clean. Now you can click carelessly on those fake-download links from SF until you reach the real source ;). The tradeoff: the possibility of labelling this release as "beta stable" is not as clear as before. This tarball requires plenty of testing, so please download it and give it a hard time! Any use of the browser serves, specially testing the new download feature and multiple windows at the same time. Get it from: http://www.dillo.org/download/dillo-0.8.1-pre2.tar.bz2 and report back to dillo-dev. Cheers Jorge.- PS: Kudos are also welcome! ;)

May 9, 2004

[Dillo-dev]compile problems on AIX + gcc

by Riccardo Mottola

Hello, I'm trying to compile 0.8.1-pre1 on AIX 4.1 : One never knows, maybe som4e progress was made :) I had still to use CFLAGS="-lpthreads" to have configure pthread working at configure. I notice the following warnings gcc -DHAVE_CONFIG_H -I. -I. -I.. -DDILLORC_SYS='"/usr/local/etc/dillorc"' -I/u sr/local/include -I/usr/local/include/gtk-1.2 -I/usr/local/include/glib-1.2 -I/u sr/local/lib/glib/include -lpthreads -D_REENTRANT -D_THREAD_SAFE -Wall -Waggreg ate-return -c `test -f 'dw_bullet.c' || echo './'`dw_bullet.c gcc: -lpthreads: linker input file unused since linking not done should I have used LDFLAGS or something else? isn't there a more elegant solution to work around this pthread regnition problem? like a configure option? Cheers, Riccardo

May 7, 2004

[Dillo-dev]Re: about gtk on solaris 2.6

by Jorge Arellano Cid

Riccardo, On Thu, 6 May 2004, Riccardo Mottola wrote: > > Hey Jorge, > > just a quick precisation. On the box where i have the old 0.7.3 dillo > which gives GTK errors, I have GIMP installed and that one works fine, I > have edited quite some images. > > SO I suspect it is something in the way dillo calls GTK that could > trigger the error, before saying GTK is bugged on that platform totally. There may be some good news for you: Try this patch: diff -pru dillo/src/dillo.c dillo-0.8.0/src/dillo.c --- dillo/src/dillo.c 2004-04-21 16:47:34.000000000 -0400 +++ dillo-0.8.0/src/dillo.c 2004-05-06 11:11:31.000000000 -0400 @@ -216,6 +216,8 @@ gint main(int argc, char *argv[]) /* Initialize GUI and parse GTK related args */ gtk_init(&argc, &argv); gdk_rgb_init(); + gtk_widget_set_default_colormap (gdk_rgb_get_cmap()); + gtk_widget_set_default_visual (gdk_rgb_get_visual()); /* Handle command line options */ while ((opt_flg = Dillo_get_opt(Options, argc, argv, &opt_argv, &idx))) { It fixes the colormap and visual detection/settings on some systems. The documentation is a bit vague about this calls, they are deprecated now, formerly suggested as initialization for most cases and removed from theGTK+2.0 API (with compatibility defines). If you're lucky, it may help with AIX too. Please test it and report. Note: The patch is in CVS now, but use a "pre1" patched tarball for the test. That asserts the use of the same configure script. Cheers Jorge.-

May 6, 2004

[Dillo-dev]downloads and pre2

by Jorge Arellano Cid

On Tue, 4 May 2004, Yves de Champlain wrote: > Hi > [...] > Everything works fine except for this : > > av_open_url: Url=>http://ftp.gnu.org/gnu/ddd/ddd-3.2.1.tar.gz< > Connecting to 199.232.41.7 > warning: Unhandled MIME type: <application/x-tar> > > ** CRITICAL **: file web.c: line 57 (a_Web_dispatch_by_type): assertion > `dw != NULL' failed. > > Of course, this does not start any download but after this, > I still get messages in the shell but I will > not have those from wget once I do "save link as" > like I have if I do "save link as" before. Effectively, a left click on a non-dillo-viewable MIME type URL triggers this error message. The code inside dillo assigns it to a "null-client" which means it continues to download but it's "ignored". This has some side effects, one of them is the transfer not being aborted (so it continues wasting bandwidth and memory). It also keeps a cache entry, so when a dpi download is requested it hits and gets fed from the cache! (not from a dpi). That's clearly a bug. This days I've been reviewing the code with a view to patch it, but it seems that a full patch (aborting the transfer, cleaning the cache entry, stopping the clients and offering a download dialog) may be too complex to debug in this pre-release testing stage. Aborting the download (which would allow for the later dpi download) looks simpler. I'm currently working on this. That, plus the two patches in CVS seem to round "pre2" and most probably become 0.8.1. Cheers Jorge.-

May 6, 2004