Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

Tim Evans wrote: Because you are running under gdb. If you run normally and arrange for the system to allow the core files (as explained in the doc) you will get one.' Now how do you know that the process 3196 is the one that serves the request? I assume that you run under httpd -X? But it doesn

Re: New to ModPerl 2

On Nov 14, 2004, at 7:04 PM, Dan Brian wrote: I'll add to your list (of potential confusion) that $r->args may not produce the expected results, and not just because of the change away from array context described at:

Re: Bug Report: seg fault with 1.29/Apache 1.3.33/RedHat 7.1

Tim Evans wrote: The fact that you refuse to give us the segfault backtrace makes it really hard to make any intelligent guesswork. There is no core file. gdb/bt on the running httpd process says: [EMAIL PROTECTED] src]# gdb httpd 3196 [...] Attaching to program: /usr/local/src/apache_1.3.33/src

Re: New to ModPerl 2

On Nov 14, 2004, at 4:06 PM, Kurt Hansen wrote: Markus Wichitill wrote: Apache::Request 2.0 (libapreq2), like mod_perl 2.0, is officially still in development, but mostly done. http://httpd.apache.org/apreq/ I second the advice to use libapreq2 if your code is based on libapreq1. I'm almost done

Re: New to ModPerl 2

Note, though, that libapreq2 will require some changes in your code, but probably less than not using libapreq. Be sure to read the documentation, especially the notes about converting from v1, for Apache::Request and Apache::Cookie at: I'll add to your list (of potential confusion) that $r->

Re: "use" etiquette in mod_perl

[ Mark, please don't forget to CC the list ] Mark S Lowe wrote: Out of these two examples, the latter is the better for performance reasons right? As I've written in the original reply, they are exactly the same. >>sub foo { >> use Bar; >>} >> >>is the same as: >> >>use Bar; >>sub foo {} The latt

Re: New to ModPerl 2

Markus Wichitill wrote: jonathan vanasco wrote: In mod_perl1, I have a handler that takes an apache request object manipulates the cookie/session data into a user, then presents the user with a page in mod_perl2, however, there is no Apache::Request (yet) -- so my code simply doesn't work at al

Re: New to ModPerl 2

Markus Wichitill wrote: jonathan vanasco wrote: In mod_perl1, I have a handler that takes an apache request object manipulates the cookie/session data into a user, then presents the user with a page in mod_perl2, however, there is no Apache::Request (yet) -- so my code simply doesn't work at al

Re: New to ModPerl 2

jonathan vanasco wrote: In mod_perl1, I have a handler that takes an apache request object manipulates the cookie/session data into a user, then presents the user with a page in mod_perl2, however, there is no Apache::Request (yet) -- so my code simply doesn't work at all. Apache::Request 2.0

New to ModPerl 2

I'm new to using mod_perl2 A few years ago I made a web application in perl cgi, moved it over to mod_perl1 about a year ago, and now I want to continue development of it in mod_perl2 I probably made this wrong to begin with, as I learned from a handful of mod_perl books In mod_perl1, I have a