Thanks for the reply; I'll see how far I get w/ resin_var_dump(). BTW
I wasn't necessarily interested in IDE debugging... but was surprised
to get to just a blank screen w/ no exceptions or errors thrown.
Will contribute what I can to the bug tracker.
On May 11, 2007, at 7:05 PM, Nam wrote:
I like to place resin_var_dump() at various points in the program as
checkpoints. It is like var_dump() but it will print to standard out
instead. It sounds primitive but it is really effective. Nevertheless,
we are looking into having IDE debugging integration in the future.
> Message: 1
> Date: Thu, 10 May 2007 16:08:48 -0600
> From: Yong Bakos <[EMAIL PROTECTED]>
> Subject: [Resin-interest] debugging quercus
> To: email@example.com
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> Hi, does anyone on the list have suggestions for getting better debug
> info while testing quercus?
> I've gotten to the point w/ a particular problem that results in a
> blank browser window, no source.
> Any ideas are appreciated.
resin-interest mailing list