Russ has asked for the wisdom of the Perl Monks concerning the following question:

This question was moved from Categorized Questions and Answers
Please do not vote for this node. It will affect the wrong user.
Thank You -- Q&AEditors

I asked yesterday about the CGI that was failing to escape. Now I've got a new interesting problem. Background: I know this code works on Linux, I've been running it for months.

I have a piece of code that says: 

print some_sub($variables);

[download]
I've put logging statements around it, since I can see it work from the debugger, but the webserver just hangs. Well, those statements point to the fact that when the sub calls: 
return ($variable);

[download]
Nothing happens.

I've since upgraded the CGI to 2.53 in order to match the other server's configuration. perl -v = 5.005_02.

Thanks for any help,
Mike

Replies are listed 'Best First'.
Re: I've returned
by btrott (Parson) on Aug 03, 2000 at 05:45 UTC
    What webserver are you running under? Are you running under Apache/mod_perl? I've had some weird situations with using print under Apache/mod_perl myself; STDOUT should be tied to the Apache request object, but on some occasions I've encountered a very similar phenomenon to what you say here: the webserver just seems to hang on the request.

    If you change that line from a print to setting a variable, then print the variable on another line, does it hang on the second line? In other words, is the print causing the problems?

    Just some suggestions.

[reply]
      The webserver is Apache 1.3.12. I don't know if mod_perl is installed, since I'm not the sysadmin for the box, and I was only installing some software. I did try changing to a variable, then printing that, but the catch is that return never does return from the sub. I was beating myself senseless since I couldn't replicate in the debugger, but I could replicate from commandline. I tried various versions of perl, from 5.004_04 to 5.005_02, and it didn't matter. I'm at my wit's end, and I haven't slept because I flew out from being on site and got home 7 hours later than planned. I'm going to kill the next person to give me shit. Mike ALL HAIL BRAK!!!
[reply]
        I have since had sleep, and replicated the environment out at the client site on my own dev. machine. It turns out that freetds used with DBD::Sybase has affected my code. I went with a basic install with the added options of --with-tdsver=7.0 and --enable-msdblib to be able to use freetds with a SQL Server 7.0 database. I installed DBD::Sybase using ctlib from freetds and could successfully connect to SQL Server 6.5/7.0. It's just that it produced problems with the return and string equality tests. Since freetds is still kind of in the whole development phase, it always goes to state, YMMV. In my case, my mileage was 0. Mike ALL HAIL BRAK!!!
[reply]

Back to Seekers of Perl Wisdom