Bug#679447: Coro segfaults

2012-07-08 Thread Marc Lehmann
On Sat, Jul 07, 2012 at 12:28:52PM +0400, Dmitry E. Oboukhov un...@debian.org wrote: Of course I (as the most people) read documentation fully if I stumble over problem. :) Unfortunately, you are unable to even answer the most basic questions I asked you, such as which OS, arch and which perl

Bug#679447: Coro segfaults

2012-07-08 Thread Marc Lehmann
On Sat, Jul 07, 2012 at 12:11:12PM +0400, Dmitry E. Oboukhov un...@debian.org wrote: 1000 +- 100 hashes with 3-4 fields in 100 asyncs... test computer has more than 4G RAM. Good luck having those 4G of ram allocated to your stack - memory management doesn't work like you think it does. You

Bug#679447: Coro segfaults

2012-07-07 Thread Dmitry E. Oboukhov
https://gist.github.com/3059829 Looking at that program, it seems you build a very large recursive data structure and then free it in one go, without providing appropriate stack space for this operation, so the segfault just means out of memory because of the deep recursion. 1000 +- 100

Bug#679447: Coro segfaults

2012-07-07 Thread Dmitry E. Oboukhov
Could You analyse the problem? Not without you first reading the documentation when configuring it and working through all the options, no :) Of course I (as the most people) read documentation fully if I stumble over problem. :) But (as I showed in my previous letter) the problem stands not

Bug#679447: Coro segfaults

2012-07-07 Thread Dmitry E. Oboukhov
https://gist.github.com/3059829 Looking at that program, it seems you build a very large recursive data structure and then free it in one go, without providing appropriate stack space for this operation, so the segfault just means out of memory because of the deep recursion. As such, the

Bug#679447: Coro segfaults

2012-07-07 Thread Dmitry E. Oboukhov
Looking at that program, it seems you build a very large recursive data structure and then free it in one go, without providing appropriate stack space for this operation, so the segfault just means out of memory because of the deep recursion. As such, the problem has nothing to do with

Bug#679447: Coro segfaults

2012-07-06 Thread Dmitry E. Oboukhov
Hi, Marc! I tried to up a project using Coro and stumbled on segfaults in perl Coro. Then I realized my project with AnyEvent (old way), but today I had some time to create test, so I've extracted part of code from my project and placed it here: https://gist.github.com/3059829 I think it

Bug#679447: Coro segfaults

2012-07-06 Thread Marc Lehmann
On Fri, Jul 06, 2012 at 08:57:33PM +0400, Dmitry E. Oboukhov un...@debian.org wrote: Could You analyse the problem? Not without you first reading the documentation when configuring it and working through all the options, no :) And obviously Coro does work for those two perl versions, so it

Bug#679447: Coro segfaults

2012-07-06 Thread Marc Lehmann
On Fri, Jul 06, 2012 at 08:57:33PM +0400, Dmitry E. Oboukhov un...@debian.org wrote: https://gist.github.com/3059829 Looking at that program, it seems you build a very large recursive data structure and then free it in one go, without providing appropriate stack space for this operation, so the