Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Re: I usually debug via...

by blue_cowdawg (Monsignor)
on Mar 13, 2005 at 17:53 UTC ( #439128=note: print w/replies, xml ) Need Help??

in reply to I usually debug via...

Repeat after me: right tool for the job... right tool for the job.

How I go about debugging any code no matter what language it is written largely depends on the nature of the bug that I'm trying to find. Cockroaches won't come out when the lights are on, so I turn the lights off and then back on again after a while and see which way they scurry. Better yet I set up a cockroach trap and trap the little vermin.

First step in debugging is defining the nature of the bug. Is the pattern of how the bug manifests itself immediately apparent. (I.E. turn on power, smoke results every time. That's pretty apparent.)

Or is the bug more sneaky? Only shows up when you are in the middle of a good sleep dreaming about <insert sex symbol here> and having a great time of it.

Is it a data driven bug? Is it a Luser driven bug? Does it depend on planet alignment?

These are all crucial questions to ask before deciding how to go about debugging a program.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://439128]
[Corion]: Hmmm. I feel a Meditation coming on. I wrote a module, DBIx::PivotQuery, which returns a table-like set of rows (AoA) but some columns are generated from column values, like in an (Excel) pivot table or a ROLLUP command
[Corion]: My current approach for subtotals involves rerunning the given query, with the hint to the user that they should use a temporary table if they want better performance.

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (9)
As of 2017-02-23 15:20 GMT
Find Nodes?
    Voting Booth?
    Before electricity was invented, what was the Electric Eel called?

    Results (347 votes). Check out past polls.