Menu
▾
▴
tilp-devel
|
From: Tijl C. <ti...@ul...> - 2003-09-16 16:52:52
|
I've ran into a problem with the grey serial cable on FreeBSD. Apparently it got introduced with the switch to gtk2, because if I run the latest versions (cables 3.7.7, files 0.5.7, calcs 4.4.7-4.5.1) there's no problem in gtk12 mode (with tilp 6.09), but there is in the gtk2 version (with tilp 6.52-6.68). Because there's no difference between the glib12 and glib2 versions of lcalcs, it appears to be with tilp itself. However, I don't know the code that good and a lot has changed between 6.09 and 6.52, so does anybody have an idea what might be the problem? A little bit more in detail, most of the time I get a timeout error while it's receiving the first byte, so sending seems to work and the calc also turns on. Very rarely it all does work properly, but I haven't found a way to reproduce that. Any clue? btw, who owns the project now roms left? |
|
From: Romain L. <rom...@wa...> - 2003-09-17 17:57:01
|
Hi Tijl and mailing list users, Tijl Coosemans a écrit : > I've ran into a problem with the grey serial cable on FreeBSD. > Apparently it got introduced with the switch to gtk2, because if I run > the latest versions (cables 3.7.7, files 0.5.7, calcs 4.4.7-4.5.1) > there's no problem in gtk12 mode (with tilp 6.09), but there is in the > gtk2 version (with tilp 6.52-6.68). > > Because there's no difference between the glib12 and glib2 > versions of lcalcs, it appears to be with tilp itself. However, I don't > know the code that good and a lot has changed between 6.09 and 6.52, so > does anybody have an idea what might be the problem? If I remember well, I didn't modified libs when switching to GTK2 but I may have done some (or too many ?) clean-up... > > A little bit more in detail, most of the time I get a timeout error > while it's receiving the first byte, so sending seems to work and the > calc also turns on. Very rarely it all does work properly, but I > haven't found a way to reproduce that. > > Any clue? Hmmm, I'm gonna to take a look at my changelog... > > btw, who owns the project now roms left? Nobody, yet ! I'm still searching for the right man who will do the good job... > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > TiLP-devel mailing list > TiL...@li... > https://lists.sourceforge.net/lists/listinfo/tilp-devel > roms. -- Romain Liévin, aka 'roms' <ro...@ti...> Site web <http://tilp.info> Messagerie instantanée (ICQ) 43585029 "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Julien B. <jb...@jb...> - 2003-09-17 18:32:02
|
Romain Lievin <rom...@wa...> wrote: >> btw, who owns the project now roms left? > > Nobody, yet ! I'm still searching for the right man who will do the > good job... Always the same problem... You'll always find people to complain about the bugs in TiLP/TiEmu, but you'll only find a few who will send patches... So, when it comes to taking over the whole project, you can't imagine the unbelievable amount of candidates we're rejecting daily... sigh. JB. --=20 N> La radio pourrait etre incluse dans ce forum. B> Dans un groupe s'appelant TV ? fr.rec.radio parle de quoi ? N> j'ai dis une connerie ? -+- in: Guide du Neuneu d'Usenet - C'est juste pour =EAtre sur... -+- |
|
From: Tijl C. <ti...@ul...> - 2003-09-17 20:58:00
|
On Wed, 17 Sep 2003 19:56:28 +0200, Romain Lievin wrote: > Hi Tijl and mailing list users, >=20 > Tijl Coosemans a =E9crit : > > I've ran into a problem with the grey serial cable on FreeBSD. > > Apparently it got introduced with the switch to gtk2, because if I > > run the latest versions (cables 3.7.7, files 0.5.7, calcs > > 4.4.7-4.5.1) there's no problem in gtk12 mode (with tilp 6.09), but > > there is in the gtk2 version (with tilp 6.52-6.68). > >=20 > > Because there's no difference between the glib12 and glib2 > > versions of lcalcs, it appears to be with tilp itself. However, I > > don't know the code that good and a lot has changed between 6.09 and > > 6.52, so does anybody have an idea what might be the problem? >=20 > If I remember well, I didn't modified libs when switching to GTK2 but > I may have done some (or too many ?) clean-up... I've made diffs from each version to the next and couldn't find anything. The fact that these libs work with TiLP 6.09 also confirms this. This all points to TiLP itself, but if I'm correct TiLP doesn't really do any "low level" stuff. It only passes options and commands on to the libs and that all seems to work ok. I've also added some debugging info and checked that the cable gets inited/opened/closed/exited properly and no problems there either. I'm running out of ideas, but I'll keep trying... |
|
From: Romain L. <rom...@wa...> - 2003-09-18 18:45:49
|
Hi, Tijl Coosemans a écrit : > On Wed, 17 Sep 2003 19:56:28 +0200, Romain Lievin wrote: > > >>Hi Tijl and mailing list users, >> >>Tijl Coosemans a écrit : >> >>>I've ran into a problem with the grey serial cable on FreeBSD. >>>Apparently it got introduced with the switch to gtk2, because if I >>>run the latest versions (cables 3.7.7, files 0.5.7, calcs >>>4.4.7-4.5.1) there's no problem in gtk12 mode (with tilp 6.09), but >>>there is in the gtk2 version (with tilp 6.52-6.68). >>> >>>Because there's no difference between the glib12 and glib2 >>>versions of lcalcs, it appears to be with tilp itself. However, I >>>don't know the code that good and a lot has changed between 6.09 and >>>6.52, so does anybody have an idea what might be the problem? >> >>If I remember well, I didn't modified libs when switching to GTK2 but >>I may have done some (or too many ?) clean-up... > > > I've made diffs from each version to the next and couldn't find > anything. The fact that these libs work with TiLP 6.09 also confirms Hmmm... Very strange ! Are you sure that tig_link.c support has not been modified ? > this. This all points to TiLP itself, but if I'm correct TiLP doesn't > really do any "low level" stuff. It only passes options and commands on No, it doesn't. > to the libs and that all seems to work ok. > > I've also added some debugging info and checked that the cable gets > inited/opened/closed/exited properly and no problems there either. > > I'm running out of ideas, but I'll keep trying... > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > TiLP-devel mailing list > TiL...@li... > https://lists.sourceforge.net/lists/listinfo/tilp-devel > roms. -- Romain Liévin, aka 'roms' <ro...@ti...> Site web <http://tilp.info> Messagerie instantanée (ICQ) 43585029 "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Tijl C. <ti...@ul...> - 2003-09-17 18:09:11
|
On Tue, 16 Sep 2003 18:13:36 +0200, Tijl Coosemans wrote: > I've ran into a problem with the grey serial cable on FreeBSD. > Apparently it got introduced with the switch to gtk2, because if I run > the latest versions (cables 3.7.7, files 0.5.7, calcs 4.4.7-4.5.1) > there's no problem in gtk12 mode (with tilp 6.09), but there is in the > gtk2 version (with tilp 6.52-6.68). > > Because there's no difference between the glib12 and glib2 > versions of lcalcs, it appears to be with tilp itself. However, I > don't know the code that good and a lot has changed between 6.09 and > 6.52, so does anybody have an idea what might be the problem? > > A little bit more in detail, most of the time I get a timeout error > while it's receiving the first byte, so sending seems to work and the > calc also turns on. Very rarely it all does work properly, but I > haven't found a way to reproduce that. > > Any clue? > > btw, who owns the project now roms left? I got it working again, but I don't have a nice solution yet. What I did is setting VMIN=1 en VTIME=0 in tig_open() in libticables, so it waits indefinitely for a byte to read. VMIN=0 and VTIME=15 (normal values) doesn't work and gives a timeout error almost immediately as in, it doesn't wait 1,5 seconds. The strange thing is that the gtk1version still works flawlessly without any of these modifications. What's going on here? Are Linux versions affected too? |
|
From: Romain L. <rom...@wa...> - 2003-09-18 18:46:54
|
Hi, Tijl Coosemans a écrit : > On Tue, 16 Sep 2003 18:13:36 +0200, Tijl Coosemans wrote: > > >>I've ran into a problem with the grey serial cable on FreeBSD. >>Apparently it got introduced with the switch to gtk2, because if I run >>the latest versions (cables 3.7.7, files 0.5.7, calcs 4.4.7-4.5.1) >>there's no problem in gtk12 mode (with tilp 6.09), but there is in the >>gtk2 version (with tilp 6.52-6.68). >> >>Because there's no difference between the glib12 and glib2 >>versions of lcalcs, it appears to be with tilp itself. However, I >>don't know the code that good and a lot has changed between 6.09 and >>6.52, so does anybody have an idea what might be the problem? >> >>A little bit more in detail, most of the time I get a timeout error >>while it's receiving the first byte, so sending seems to work and the >>calc also turns on. Very rarely it all does work properly, but I >>haven't found a way to reproduce that. >> >>Any clue? >> >>btw, who owns the project now roms left? > > > I got it working again, but I don't have a nice solution yet. What I did > is setting VMIN=1 en VTIME=0 in tig_open() in libticables, so it waits > indefinitely for a byte to read. VMIN=0 and VTIME=15 (normal values) > doesn't work and gives a timeout error almost immediately as in, it > doesn't wait 1,5 seconds. The strange thing is that the gtk1version > still works flawlessly without any of these modifications. > What's going on here? Are Linux versions affected too? Could you see whether the timeout value is passed fine to the lib. It may explain your problem... BTW, are you 'root' ? > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > TiLP-devel mailing list > TiL...@li... > https://lists.sourceforge.net/lists/listinfo/tilp-devel > roms. -- Romain Liévin, aka 'roms' <ro...@ti...> Site web <http://tilp.info> Messagerie instantanée (ICQ) 43585029 "Linux, y'a moins bien mais c'est plus cher !" |
|
From: Tijl C. <ti...@ul...> - 2003-09-19 19:38:29
|
On Thu, 18 Sep 2003 20:46:24 +0200, Romain Lievin wrote: > > I got it working again, but I don't have a nice solution yet. What I > > did is setting VMIN=1 en VTIME=0 in tig_open() in libticables, so it > > waits indefinitely for a byte to read. VMIN=0 and VTIME=15 (normal > > values) doesn't work and gives a timeout error almost immediately as > > in, it doesn't wait 1,5 seconds. The strange thing is that the > > gtk1version still works flawlessly without any of these > > modifications. What's going on here? Are Linux versions affected > > too? > > Could you see whether the timeout value is passed fine to the lib. It > may explain your problem... No problem there. Hardcoding the timeout value into the lib gives the same problem, even if I set it to 50, "read" returns immediately with no bytes read and thus giving a time out error. Does that mean it reads an EOF? > BTW, are you 'root' ? yes. |
|
From: Tijl C. <ti...@ul...> - 2003-09-20 14:35:27
|
I found what the problem was, but I haven't solved it (yet). The problem shows up when libxml2 is compiled with threads enabled. In Linux that means it is linked against libpthread(?), but in FreeBSD you have to add the -pthread flag to gcc so it will link against libc_r instead of libc (libc_r is the reentrant version of libc). Because tilp depends on libxml2 (through libglade2), it is linked against libc_r too, which seems to give problems. Anybody an idea to solve this? Perhaps I should ask some freebsd hackers, because this is way over the top of my head... |
|
From: Romain L. <rom...@wa...> - 2003-09-22 17:27:44
|
Hi, Tijl Coosemans a écrit : > I found what the problem was, but I haven't solved it (yet). > > The problem shows up when libxml2 is compiled with threads enabled. In > Linux that means it is linked against libpthread(?), but in FreeBSD you > have to add the -pthread flag to gcc so it will link against libc_r > instead of libc (libc_r is the reentrant version of libc). > > Because tilp depends on libxml2 (through libglade2), it is linked > against libc_r too, which seems to give problems. It's nasty... > > Anybody an idea to solve this? Perhaps I should ask some freebsd > hackers, because this is way over the top of my head... Yes, I think. > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > TiLP-devel mailing list > TiL...@li... > https://lists.sourceforge.net/lists/listinfo/tilp-devel > roms -- Romain Liévin, aka 'roms' <ro...@ti...> Site web <http://tilp.info> Messagerie instantanée (ICQ) 43585029 "Linux, y'a moins bien mais c'est plus cher !" |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X