Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: Yet another debugging technique Date: Wed, 23 Apr 2014 08:47:07 -0700 Organization: Canadian Mind Products Lines: 18 Message-ID: References: <99ffl9d6hmvrgh58bbc58rus6f8n016gdg@4ax.com> <5357d24e$0$2897$e4fe514c@news.xs4all.nl> Reply-To: Roedy Green NNTP-Posting-Host: K2Qzzs3EAqXk5RLzfhxcSw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: ForteAgent/7.20.32.1218 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:28201 On Wed, 23 Apr 2014 16:46:37 +0200, Silvio wrote, quoted or indirectly quoted someone who said : >Unless you would have some really crappy code most IO calls in an HTML >generating application would be inside a very small general purpose >utility class. You would need an entire stack trace at every output >position to be able to actually pinpoint a bug. I think, in practice, the depth of the stack you want too sample is constant. Perhaps if it is variable, the code would have to set it dynamically, yuch! Perhaps the snapshot taker could be given a list of methods NOT of interest. When it hits one, it snapshots one deeper in the stack. -- Roedy Green Canadian Mind Products http://mindprod.com "Don't worry about people stealing an idea; if it's original, you'll have to shove it down their throats." ~ Howard Aiken (born: 1900-03-08 died: 1973-03-14 at age: 73)