Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
El 20/06/11 22:06, Len Jaffe escribió: Hmm... make sure all those libraries are readable. make sure you can resolve all the dependencies in those 6 libraries too. Len. All are readable and resolvable, I think all of them are pretty standard system libraries. I'm resolving them as a normal user, so the very fact that ldd can open and check them indicates that permissions are OK. [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-TnpClr]$ ldd ./blib/arch/auto/HTTP/HeaderParser/XS/XS.so linux-gate.so.1 = (0x00b8) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x00c88000) libm.so.6 = /lib/libm.so.6 (0x0072e000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x00766000) libc.so.6 = /lib/libc.so.6 (0x009b3000) /lib/ld-linux.so.2 (0x00682000) [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-TnpClr]$ ldd /usr/lib/libstdc++.so.6 linux-gate.so.1 = (0x00203000) libm.so.6 = /lib/libm.so.6 (0x00837000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x00925000) libc.so.6 = /lib/libc.so.6 (0x006a6000) /lib/ld-linux.so.2 (0x00682000) [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-TnpClr]$ ldd /lib/libm.so.6 /lib/ld-linux.so.2 (0x00682000) linux-gate.so.1 = (0x00e82000) libc.so.6 = /lib/libc.so.6 (0x006a6000) [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-TnpClr]$ ldd /lib/libgcc_s.so.1 linux-gate.so.1 = (0x00cab000) libc.so.6 = /lib/libc.so.6 (0x006a6000) /lib/ld-linux.so.2 (0x00682000) [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-TnpClr]$ ldd /lib/libc.so.6 /lib/ld-linux.so.2 (0x00682000) linux-gate.so.1 = (0x00f45000) How can I trace the loading and errors of blib/arch/auto/HTTP/HeaderParser/XS/XS.so? Regards Jorge ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
We're nearing the outer limits of my experience. I'd try strace, it might tell you which shared lib is failing to load. Len. On Tue, Jun 21, 2011 at 6:29 AM, Jorge Gonzalez jorge.gonza...@daikon.eswrote: El 20/06/11 22:06, Len Jaffe escribió: Hmm... make sure all those libraries are readable. make sure you can resolve all the dependencies in those 6 libraries too. Len. All are readable and resolvable, I think all of them are pretty standard system libraries. I'm resolving them as a normal user, so the very fact that ldd can open and check them indicates that permissions are OK. [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-**TnpClr]$ ldd ./blib/arch/auto/HTTP/**HeaderParser/XS/XS.so linux-gate.so.1 = (0x00b8) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x00c88000) libm.so.6 = /lib/libm.so.6 (0x0072e000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x00766000) libc.so.6 = /lib/libc.so.6 (0x009b3000) /lib/ld-linux.so.2 (0x00682000) [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-**TnpClr]$ ldd /usr/lib/libstdc++.so.6 linux-gate.so.1 = (0x00203000) libm.so.6 = /lib/libm.so.6 (0x00837000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x00925000) libc.so.6 = /lib/libc.so.6 (0x006a6000) /lib/ld-linux.so.2 (0x00682000) [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-**TnpClr]$ ldd /lib/libm.so.6 /lib/ld-linux.so.2 (0x00682000) linux-gate.so.1 = (0x00e82000) libc.so.6 = /lib/libc.so.6 (0x006a6000) [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-**TnpClr]$ ldd /lib/libgcc_s.so.1 linux-gate.so.1 = (0x00cab000) libc.so.6 = /lib/libc.so.6 (0x006a6000) /lib/ld-linux.so.2 (0x00682000) [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-**TnpClr]$ ldd /lib/libc.so.6 /lib/ld-linux.so.2 (0x00682000) linux-gate.so.1 = (0x00f45000) How can I trace the loading and errors of blib/arch/auto/HTTP/** HeaderParser/XS/XS.so? Regards Jorge __**_ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-**bin/mailman/listinfo/catalysthttp://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/** catalyst@lists.scsys.co.uk/http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ -- lenja...@jaffesystems.com 614-404-4214 Proprietor: http://www.theycomewithcheese.com/ - An Homage to Fromage Asst. Scoutmaster Troop 156 - www.bsatroop156.org - webmas...@bsatroop156.org ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
El 21/06/11 15:33, Len Jaffe escribió: We're nearing the outer limits of my experience. I'd try strace, it might tell you which shared lib is failing to load. Len. Been there, done that. In fact it was almost the first thing I tried. No news. It mmaps correctly all needed libraries and seems to jump to execute it, then returns with an error. It would be great to know the library function that the perl code jumps into when loading an XS shared object. This would allow us to follow the control flow inside the XS source and try to spot the offender. It seems that this function might be boot_HTTP__HeaderParse__XS (you can check symbols in the .so with 'nm'), but I can't find its definition anywhere but in HTTPHeaders.c, which is autogenerated from HTTPHeaders.xs. I set PERL_DL_DEBUG=1 before executing again 'make test', which gives a bit more info, but not nearly enough. I'm stuck. I'll explore some other ways, like disabling Catalyst::Engine::HTTP::Prefork's use of this module. I'll keep you informed. (desperate) Regards :-) J. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
It seems this one was caught some 10 days ago: http://www.cpantesters.org/cpan/report/e78f810a-9422-11e0-b1d0-9dea81bb81c4 The error which appears in the report is _exactly_ the one I'm stepping on. J. El 21/06/11 16:32, Jorge Gonzalez escribió: El 21/06/11 15:33, Len Jaffe escribió: We're nearing the outer limits of my experience. I'd try strace, it might tell you which shared lib is failing to load. Len. Been there, done that. In fact it was almost the first thing I tried. No news. It mmaps correctly all needed libraries and seems to jump to execute it, then returns with an error. It would be great to know the library function that the perl code jumps into when loading an XS shared object. This would allow us to follow the control flow inside the XS source and try to spot the offender. It seems that this function might be boot_HTTP__HeaderParse__XS (you can check symbols in the .so with 'nm'), but I can't find its definition anywhere but in HTTPHeaders.c, which is autogenerated from HTTPHeaders.xs. I set PERL_DL_DEBUG=1 before executing again 'make test', which gives a bit more info, but not nearly enough. I'm stuck. I'll explore some other ways, like disabling Catalyst::Engine::HTTP::Prefork's use of this module. I'll keep you informed. (desperate) Regards :-) J. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
well, that's something at least. On Tue, Jun 21, 2011 at 10:46 AM, Jorge Gonzalez jorge.gonza...@daikon.eswrote: It seems this one was caught some 10 days ago: http://www.cpantesters.org/**cpan/report/e78f810a-9422-** 11e0-b1d0-9dea81bb81c4http://www.cpantesters.org/cpan/report/e78f810a-9422-11e0-b1d0-9dea81bb81c4 The error which appears in the report is _exactly_ the one I'm stepping on. J. El 21/06/11 16:32, Jorge Gonzalez escribió: El 21/06/11 15:33, Len Jaffe escribió: We're nearing the outer limits of my experience. I'd try strace, it might tell you which shared lib is failing to load. Len. Been there, done that. In fact it was almost the first thing I tried. No news. It mmaps correctly all needed libraries and seems to jump to execute it, then returns with an error. It would be great to know the library function that the perl code jumps into when loading an XS shared object. This would allow us to follow the control flow inside the XS source and try to spot the offender. It seems that this function might be boot_HTTP__HeaderParse__XS (you can check symbols in the .so with 'nm'), but I can't find its definition anywhere but in HTTPHeaders.c, which is autogenerated from HTTPHeaders.xs. I set PERL_DL_DEBUG=1 before executing again 'make test', which gives a bit more info, but not nearly enough. I'm stuck. I'll explore some other ways, like disabling Catalyst::Engine::HTTP::**Prefork's use of this module. I'll keep you informed. (desperate) Regards :-) J. __**_ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-**bin/mailman/listinfo/catalysthttp://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/** catalyst@lists.scsys.co.uk/http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ __**_ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-**bin/mailman/listinfo/catalysthttp://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/** catalyst@lists.scsys.co.uk/http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ -- lenja...@jaffesystems.com 614-404-4214 Proprietor: http://www.theycomewithcheese.com/ - An Homage to Fromage Asst. Scoutmaster Troop 156 - www.bsatroop156.org - webmas...@bsatroop156.org ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
Well, it looks like the Catalyst::Engine::HTTP::Prefork module will be abandoned in the near future, so some guru on #catalyst advised me to move on to Starman/PSGI for a real high performance preforking server for Catalyst. Which I did. My application is now running full tilt. It took me less than 10 minutes to convert (:-) my app to Starman. Thanks, Len, for your time. Regards Jorge El 21/06/11 16:46, Jorge Gonzalez escribió: It seems this one was caught some 10 days ago: http://www.cpantesters.org/cpan/report/e78f810a-9422-11e0-b1d0-9dea81bb81c4 The error which appears in the report is _exactly_ the one I'm stepping on. J. El 21/06/11 16:32, Jorge Gonzalez escribió: El 21/06/11 15:33, Len Jaffe escribió: We're nearing the outer limits of my experience. I'd try strace, it might tell you which shared lib is failing to load. Len. Been there, done that. In fact it was almost the first thing I tried. No news. It mmaps correctly all needed libraries and seems to jump to execute it, then returns with an error. It would be great to know the library function that the perl code jumps into when loading an XS shared object. This would allow us to follow the control flow inside the XS source and try to spot the offender. It seems that this function might be boot_HTTP__HeaderParse__XS (you can check symbols in the .so with 'nm'), but I can't find its definition anywhere but in HTTPHeaders.c, which is autogenerated from HTTPHeaders.xs. I set PERL_DL_DEBUG=1 before executing again 'make test', which gives a bit more info, but not nearly enough. I'm stuck. I'll explore some other ways, like disabling Catalyst::Engine::HTTP::Prefork's use of this module. I'll keep you informed. (desperate) Regards :-) J. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
On Tue, Jun 21, 2011 at 11:51 AM, Jorge Gonzalez jorge.gonza...@daikon.eswrote: Well, it looks like the Catalyst::Engine::HTTP::**Prefork module will be abandoned in the near future, so some guru on #catalyst advised me to move on to Starman/PSGI for a real high performance preforking server for Catalyst. Which I did. My application is now running full tilt. It took me less than 10 minutes to convert (:-) my app to Starman. Thanks, Len, for your time. You're very welcome. You're also on the hook if I ever need Starman help. Len. -- lenja...@jaffesystems.com 614-404-4214 Proprietor: http://www.theycomewithcheese.com/ - An Homage to Fromage Asst. Scoutmaster Troop 156 - www.bsatroop156.org - webmas...@bsatroop156.org ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
Reading DynaLoader.pm line 213 it says that very often programs fail saying that there's an error in there, but it's really the XS initialization code for the module which is really failing. Since my XS skills are, well, close to zero, I can't trace anything there. How can I trace the loading of an XS module? I have tried even with strace, but I didn't see anything... I just worked through an XS loader issue last week. It typically has to do with unsatisfied dependencies in the web of shared libs that you're trying to load. so find the .so in question, and run ldd on it. ldd will list all of that library's dependencies, and tell you if it can find them or not. If it can't then you probably need to add a few libs to your LD_LIBRARY_PATH variable. Len. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
Thaks Len. I already had done that before posting, no success. It looks like all LD dependencies are satisfied: (after 'make test'): [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-TnpClr]$ find . -name *.so ./blib/arch/auto/HTTP/HeaderParser/XS/XS.so [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-TnpClr]$ ldd ./blib/arch/auto/HTTP/HeaderParser/XS/XS.so linux-gate.so.1 = (0x0040c000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x0011) libm.so.6 = /lib/libm.so.6 (0x00d5f000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x0061b000) libc.so.6 = /lib/libc.so.6 (0x001fb000) /lib/ld-linux.so.2 (0x00682000) Any more ideas? Thanks J. El 20/06/11, Len Jaffe lenja...@jaffesystems.com escribió: Reading DynaLoader.pm line 213 it says that very often programs fail saying that there's an error in there, but it's really the XS initialization code for the module which is really failing. Since my XS skills are, well, close to zero, I can't trace anything there. How can I trace the loading of an XS module? I have tried even with strace, but I didn't see anything... I just worked through an XS loader issue last week. It typically has to do with unsatisfied dependencies in the web of shared libs that you're trying to load. so find the .so in question, and run ldd on it. ldd will list all of that library's dependencies, and tell you if it can find them or not. If it can't then you probably need to add a few libs to your LD_LIBRARY_PATH variable. Len. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Problem in compiling Catalyst::Engine::HTTP::Prefork due to HTTP::HeaderParser::XS
On Mon, Jun 20, 2011 at 3:04 PM, Jorge Gonzalez jorge.gonza...@daikon.eswrote: Thaks Len. I already had done that before posting, no success. It looks like all LD dependencies are satisfied: (after 'make test'): [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-**TnpClr]$ find . -name *.so ./blib/arch/auto/HTTP/**HeaderParser/XS/XS.so [jorgegv@desarrollo3 HTTP-HeaderParser-XS-0.20-**TnpClr]$ ldd ./blib/arch/auto/HTTP/**HeaderParser/XS/XS.so linux-gate.so.1 = (0x0040c000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x0011) libm.so.6 = /lib/libm.so.6 (0x00d5f000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x0061b000) libc.so.6 = /lib/libc.so.6 (0x001fb000) /lib/ld-linux.so.2 (0x00682000) Any more ideas? Hmm... make sure all those libraries are readable. make sure you can resolve all the dependencies in those 6 libraries too. Len. -- lenja...@jaffesystems.com 614-404-4214 Proprietor: http://www.theycomewithcheese.com/ - An Homage to Fromage Asst. Scoutmaster Troop 156 - www.bsatroop156.org - webmas...@bsatroop156.org ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
