Re: Debugging and Error Trace

On 30 Okt., 07:22, George Neuner <gneuner2/@/comcast.net> wrote:

I've rarely found back traces useful other than to tell me what
function calls led to the problem. I've never seen a back trace that
included enough information to recreate the problem so I can step
through and watch.

Bad luck for you. With Eiffel 90% of the crashs with backtraces are
extremely helpfull, 80% can fix the problem immediately. This is the
benefit
of DBC and printing out the local variables not only the function
names.

The latter is indeed almost useless.

.

Relevant Pages

  • Re: Why Buy a Converter?
    ... |> Lots of prime time game shows with Duel being the best IMO. ... I did find a few shows in his list that I might watch at times (Law and ... Order, Cold Case, Without a Trace, CSI). ...
    (alt.tv.tech.hdtv)
  • Re: Why I/Oread is a low Num on the exec. Plan but very high on tr
    ... Well they both show 3 million at the trace and the same IOs. ... > Andrew J. Kelly SQL MVP ... I was actually using the migration time to recreate indexes. ... >> very low number before I do the db reindex. ...
    (microsoft.public.sqlserver.server)
  • Re: [RFC 5/7] LTTng instrumentation mm
    ... operations and let the trace analyzer figure out the mappings. ... recreate the kernel structures from the traced information, ... instrument memory allocation/free. ... information needed to recreate the memory mappings in the kernel at any ...
    (Linux-Kernel)
  • Re: Rainbow Portal Null reference
    ... exception. ... to watch and/or trace. ... Object reference not set to an instance of an object. ...
    (microsoft.public.dotnet.framework)
  • Re: How to avoid shooting myself in the foot (XOTcl)
    ... Concerning Tcl command traces: ... Gerald noticed correctly, in the case with the recreate, the Tcl ... not invoking a command delete trace at this point is a bug. ...
    (comp.lang.tcl)