[Help-gnunet] New w32 problems

[Christian Drechsler]

Hi,

the new build seems to have some new problems:

- First, it still keeps steadily growing. Not as fast fast as before, but
it does.

- gnunetd does not daemonize when started from cmd.exe (I guess this was
also the case in the previous version)

The rest seems to be a problem complex not easy to nail down. I'll
describe evrything I have experienced:

After the first launch (via gnunet-gtk), gnunetd ran for some hours.
Everything seemed to be ok; I tested some searches with gnunet-search. It
worked as expected.

I then wanted to start gnunet-gtk. It started drawing it's window and
froze before that was ready. I retried several times and also waited
several minutes, nothing happened. I then killed gnunetd and retried - it
worked. gnunet-stats produced the expected output. I then started a
search with gnunet-gtk. It didn't produce any results, although it was
the same keyword I had found several hundred entries with on the same day
before with gnunet-search. I tried gnunet-stats, but that didn't produce
any output. It worked again when I killed and restartet gnunetd. 

Ah! After some testing I found out what the problem seems to be: A search
for keyword audio/mp3. Everything else works great, but with that exact
keyword, the following happens: I see two tcp connections between client
and gnunetd, one with 4 bytes transmitted, one with 32 bytes. Both remain
unanswered. From that point on, gnunetd will not answer any queries from
local clients. It seems as if it freezes when confronted with a
gnunet-stats-query afterwards, but I haven't tested that thoroughly.
(Freeze==doesn't use much CPU and no network at all.)

I find it quite confusing that it is only that keyword - it's not the
slash, as I had thought, I tried hell/yes and it worked perfectly (no
results, though, of course :-) ). The failure with audio/mp3 is
reproducable, though. And even more strange: I _got_ big results for that
query earlier this day, and it seemed to work. _Very_ strange indeed. ?-)

I hope this helps. :-)

Regards,

Christian

P.S.: Should I file stuff like that in Mantis in the future, or do you
like it better here?

pgpaCzKfpCAvF.pgp
Description: PGP signature