"i am not aware of the code and dont want to understand it either please help!!!!

If you have no interest in understanding the code, forget about debugging it. What help do you expect? Otherwise read and understand the code and then look at Debugging and Optimization from the tutorials section.

See also How do I compose an effective node title? and How do I post a question effectively?. Consider replacing your keyboard, your exclamation mark key seems faulty.

You can't find grammatical errors in Mark Twain without looking inside the book. Continuity errors would require even greater research. If you don't want to do it yourself hire someone who is more willing / motivated. There is no fully automatic bug finder/fixer.

Also, I'm guessing that we're stumbling over a cultural and language problem here - I'm guessing that what you meant to say was "This program is complex; I'm pressed for time and wondering if there are any tools to help me debug the problem automatically. I don't really understand the code at present, and was hoping I could get a recommendation as to what to do."

You have made an unfortunate impression with the phrases "not aware" and "don't want to understand"; I'm guessing you meant "not familiar" (as in "I don't know this particular piece of code well" and "am hoping I can get a hand on fixing it without having to completely analyze it". The forms you chose in English imply that you are trying to not have to do any work at all to solve the problem, which I'm going to assume is not true. The Perlmonks culture is very much "we help those who help themselves"; if we see evidence that you've been trying to solve the problem, we'll gladly jump in and try to help you. If on the other hand we get the impression that you are simply dropping a problem in our laps (which the language above implies), then the reception is likely to be cold if not hostile.

What little help I can offer you: you may find that you can, with some reading of the code, focus in on the areas where the problem is probably occurring, and use the Perl debugger to stop execution there and examine what the code is doing at those points. This may be sufficient to solve the problem without requiring you to completely understand the program from top to bottom right now.

If, however, this isn't a one-off piece of code you'll never use again, I encourage you to spend the time to understand it so that you will have a head start on fixing problems in the code in the future. Good luck.

totally agree with you pemungkah
thanks for understanding my situation