Updates:
Status: Fixed
Comment #19 on issue 410 by benoit.m...@gmail.com: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
OK, marked as fixed.
--
You received this message because this project is configured to send all
issue notifications to this address.
Comment #18 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
No problem for the delay, r5584 works ok, with and without _Read event
present.
Thanks.
--
You received this message because this project is configured to send all
i
Comment #17 on issue 410 by benoit.m...@gmail.com: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
HttpClient now calls the Read event while there is something to read. But
it's stupid do that if there is no Read event handler!
In revision #5584, this behavior is
Comment #16 on issue 410 by benoit.m...@gmail.com: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
Sorry for not answering, my PC was dead. I have a new one now, and I will
look at the problem.
--
You received this message because this project is configured to se
Comment #15 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
I mean uncomment the _Read code...
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your
Comment #14 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
While trying to extract a demo project to show the problem I figured out
the reason for the hangs.
Try attached project, if you don't code a _Read event for a async
ht
Comment #13 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
Can we please rollback the changes done in revision 5542?
Just for one request of being able to do oauth request, the whole component
and thuse gambas became useless..
Comment #12 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
Attached latest valgrind output.
Leaks everywhere, can someone help me?
Attachments:
valgrind.log.tar.gz 132 KB
--
You received this message because this proje
Comment #11 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
No it's still unstable.
My project which had 24/7 stability for months in a row now only runs a few
minutes.
If this isn't fixed soon it's another big appointment using
Comment #10 on issue 410 by adrien.p...@gmail.com: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
Hello,
I had a similar issue with gb.net.curl recently (valgrind logs are close),
and I fixed it in revision #5581.
Can you tell me if this revision solved your prob
Comment #9 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
It does the call against gambas xmlrpc server code.
--
You received this message because this project is configured to send all
issue notifications to this address.
You
Comment #8 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
And the Gambas code triggering the crash in http client r5542 is this:
When sValue = "" it crashes...
Any other value is ok.
It crashes on cRpc.Call() (which does http cli
Comment #7 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
The first signal 11 crash in this ticket is caused by the changes done in
gb.net.curl revision 5542, revision 5541 works without crashing.
These changes were done after r
Comment #6 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
Attached the valgrind memcheck-full output of starting the project, let it
run for a second or 10 and then run the signal 11 code.
Attachments:
valgrind.tar.gz
Comment #5 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
You see that in the gdb output, that it copies 3MB?
Thats quite odd, while the code I use simply calls the google api to create
a dial image of a few hundreds kb.
This is
Updates:
Status: NeedsInfo
Comment #4 on issue 410 by benoit.m...@gmail.com: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
The curl exit crash has been fixed upstream (see issue 405).
The other crash occurs while trying to copy 3MB of data from the interna
Comment #3 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
About the knowne exit bug in curl, it's the curl available in 13.04, it
bleeding new, would be bad if that's the one in release version.
Any references to bug report?
Ab
Updates:
Status: Accepted
Labels: -Version Version-TRUNK
Comment #2 on issue 410 by benoit.m...@gmail.com: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
The signal 11 in curls exit code is known to be a bug in the curl library.
--
You received thi
Comment #1 on issue 410 by r...@cyberjunky.nl: Signal 11 in gb.net.curl
http://code.google.com/p/gambas/issues/detail?id=410
There is also a signal 11 bug in curls exit code.
warning: no loadable sections found in added symbol-file system-supplied
DSO at 0x77ffa000
[Thread debugging using
19 matches
Mail list logo
