|
in reply to Re^2: CGI Perl output cut with xampp
in thread CGI Perl output cut with xampp
If the problem seems to correspond to the output size, maybe just creating a program that outputs that much data already reproduces the problem?
I'm not sure what your expectation is how we could help you here better. We are not clairvoyant and you have not shown us any approach to reproducing the problem nor a succinct description of where/how the problem happens at all.
If you are talking about a webpage, maybe telling us which of the many, many Perl scripts in the (not linked) Github repository is the one that is problematic allows somebody here to spot the problem a bit better. But I recommend to post the relevant code after shortening it to say 20-30 lines instead of linking to some github repository. Please also make sure that the problem still persists after shortening the code. |
Re^4: CGI Perl output cut with xampp
by toohoo (Beadle) on Jul 05, 2016 at 13:46 UTC
|
Hi,
I guess I do not really understand, what you mean. If i cut the code, it wont work anymore.
I can try this evening to generate a big enough database.
The starting script is faq.pl . The Script that puts all code out is editfaq.pl . I have compared it yet but cannot find relevant differences.
BTW: I never did say you have to be clairvoyant, I find it disturbing to imply that I did it or "might" want to do it.
| [reply] |
|
|
If i cut the code, it wont work anymore.
Then maybe you cut the wrong parts? The idea is to keep removing stuff until the script starts working. Most likely, then the last thing you removed is a thing responsible for part of the problem. You then add that thing back, verify that the problem reappears, and then start removing other things.
If you keep at this process, you will end up with a short, self-contained example that is no longer than 30 lines and still reproduces the problem.
There are two ways of debugging something. One way is to be clairvoyant and the other is to reproduce the problem. So far, you haven't really helped us with the approach of reproducing the problem, so the only other approach that remains is to divine the problem through clairvoyance, with which I cannot really help.
| [reply] |
|
|
BTW: I never did say you have to be clairvoyant, I find it disturbing to imply that I did it or "might" want to do it.
Take it easy, neither Corion nor anyone else claimed that you said that.
With the quantity of information you provided, it's very difficult to figure out what your problem is, and you haven't provided a mean to reproduce it. So, in that sense, our only options are at best guess work, shots in the dark or being clairvoyant. That's it, nothing more, no pejorative or derogatory intent implied.
BTW, I can tell you that there is no such output limitation in Perl, I am frequently writing files with dozens of GB. As for xampp, I have no idea, I don't even know what it is.
| [reply] |
|
|
I have no idea what the chances are that you'll find someone who's had exactly the same problem and knows the answer off the top of their head. If we can't reproduce the problem, we can only guess what the problem is. You named "faq.pl" and "editfaq.pl" as the source of the problem. Both of those scripts include the files "thpl.pl" and "webtools.pl", each of those are over a thousand lines in length. I doubt most people will have the time to wade through those files. So your best bet to reach a wider audience is to give us something short with which we can reproduce your problem.
How would you debug this if you were in a remote location with no Internet to ask? You'd first isolate the problem by narrowing down the source of the issue. Cut away pieces of code, if the problem goes away, you know you just removed something essential to the problem, if not, keep cutting. Insert debug statements, see how far the code runs, and so on. See http://sscce.org/ and the Basic debugging checklist.
| [reply] |
|
|
| [reply] |
|
|
thanks all for the help.
I did not have time yesterday to create a version publicly to re-test the issue. I will look forward to do this. Then I will point to it.
The most known rules of software developing I know - I think. I develop since some years.
It is clear to me, that without a showing of the effect it is difficult to understand.
I appreciate your engagement so far, that you are willing to help me further in my problem. But as I just stated first time, I only wanted to know, if anybody has known limitations of the Perl included in XAMPP or anybody has known limitations of the XAMPP in relation to Perl. Allthough no one has said this, I guess the are none.
As may be to mention the XAMPP is downloaded from portableapps.com
I will look forward to give further details.
regards
| [reply] |
|
|
"I only wanted to know, if anybody has known limitations of the Perl included in XAMPP or anybody has known limitations of the XAMPP in relation to Perl.
I know of nothing specific to XAMPP. Did you ask them? Consider not using cgi-lib, try a modern framework e.g. Mojolicious/Dancer.
| [reply] |
|
|
| [reply] |
|
|
|
|
|
|
