So, to sum it up, code that we don't know is operating on data we haven't seen and failing in an unspecified way. I'm sure I'm not the only monk shrugging helplessly now, thinking "how exactly do you think we're supposed to help you?"

Please give us something to work with. If your code's too large to post, whittle it down to the a simple test case that exhibits the problematic behavior. If your input files are too large to post (or confidential), provide some simpler ones that show the problem.

Attempting to do this may be instructive in itself: perhaps while simplifying, you'll realize what the problem is. Or perhaps you'll cross a threshold below which it'll work, which may provide clues as to what's going wrong (and why, and how to fix it). Even if you can successfully create a small, postable test case, perhaps it'll be simple enough that you'll see the issue yourself. If not, at least the monks will have something to work with.

Some general tips and links for asking questions, copied from my homenode:

• How to ask questions (based on ww, Re: Replace key pair value from one to other file):

  1. Read the instructions ("Asking questions effectively", "Formatting your write-up", below).
  2. Read the documentation.
  3. Show effort. Write some code; at the very least, try. Help is free; doing your job for you is not.
  4. Show us your code.
  5. Describe failures, expected results, and actual results.
  6. If applicable, show us verbatim (!) error messages/warnings.
  7. If applicable, give us some sample data.
  8. Give us the larger picture: tell us what you want to achieve, not just how you decided to go about achieving it. There may be better ways of doing it that you haven't contemplated.

• Asking questions effectively:

  • On asking for help
  • How do I post a question effectively?
  • How do I compose an effective node title?
  • I know what I mean. Why don't you?
  • How (Not) To Ask A Question
  • Clean your room
  • XY Problem
  • How to RTFM
  • The SSCCE: Short, Self Contained, Correct (Compilable) Example
  • A few guidelines for good code, from Laurent_R: Re: text files are printed after the end of second module
  • Where should I post X? / PerlMonks Sections

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.