Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of wbwolen@gmail.com designates
 64.233.184.237 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=mi7HtUpz67rrkzppfOwE8VF3qktRyWhMCKH4Zkse8W/uf5KLPWBRyUIPrmqQ3E4vEr7iMIlJ9J/JPi5D1LRIXsMTbo0qHMSWAbtvDaugesgCLJgMLvt8NTaSJjzA2ge6TgfK5NCDBwyU+SL5sZ0vZZUFz5oBbExOov7HFy4jia8=
Message-ID: <e8ce6bc30706131135kf3c1471geaa4bcc8c62e9a8c@mail.gmail.com>
Date: Wed, 13 Jun 2007 11:35:41 -0700
From: "Bwolen Yang" <wbwolen@gmail.com>
To: hadoop-dev@lucene.apache.org
Subject: Re: \r\n problem in LineRecordReader.java
In-Reply-To: <46701CEA.30305@yahoo-inc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <e8ce6bc30706121035q18723d3v77721087c850e2fc@mail.gmail.com>
	 <e8ce6bc30706122228w17cedb6as83b2c93ae0f82d65@mail.gmail.com>
	 <466F974E.90403@yahoo-inc.com>
	 <e8ce6bc30706130835rbcb7291q64744db9f2fe0470@mail.gmail.com>
	 <e8ce6bc30706130843s3f53ab0cj4f9e953ada7a53db@mail.gmail.com>
	 <46701CEA.30305@yahoo-inc.com>

> You should file a Jira on this (with your traces etc).

done.
  https://issues.apache.org/jira/browse/HADOOP-1489

a couple questions.

- When including code/stack trace, my input was nicely indented, but
after submission, somehow the text formatting fields are all mess up.
(e.g., the entire code segment became one line).   Is attachment the
only way to do this right?

- To track this, I essentially was doing "printf" debugging.   It is
rather slow/painful.  Is there a way to get suspend the tasks, which
will then allow people to attach a debugger in time to trace thru the
execution.   If not, how do people generally debug problems like this?

I generally find the ability to debugger-attach to programs and just
roam around the stack helps greatly in understanding complex programs
quickly (even if I am not looking for bugs).


bwolen