B
Bjoern
I currently have to debug (somebody elses) very messy code, and instead
of bemoaning my fate, I decided I should wonder if there actually are
some common wisdoms as to how to approach such a problem? I've read a
lot about common software engineering tasks (design patterns etc), but
what about this everyday problem? Is there a debugging pattern?
Since it's J2ME projects, I am also very limited in the logging or
debugging capabilities. Often I don't have an emulator for a particular
device, so I can't print many logging statements. The debugger also
crashes many emulators.
So I am curious if there is a proper way to approach this, or is trial
and error all I can do?
Even 'binary search' (my first thought) is difficult to do, since code
doesn't always execute in a linear way.
Many thanks in advance!
Bjoern
--
Let's not weep for their evil deeds,
but for their lack of imagination
(Nick Cave)
of bemoaning my fate, I decided I should wonder if there actually are
some common wisdoms as to how to approach such a problem? I've read a
lot about common software engineering tasks (design patterns etc), but
what about this everyday problem? Is there a debugging pattern?
Since it's J2ME projects, I am also very limited in the logging or
debugging capabilities. Often I don't have an emulator for a particular
device, so I can't print many logging statements. The debugger also
crashes many emulators.
So I am curious if there is a proper way to approach this, or is trial
and error all I can do?
Even 'binary search' (my first thought) is difficult to do, since code
doesn't always execute in a linear way.
Many thanks in advance!
Bjoern
--
Let's not weep for their evil deeds,
but for their lack of imagination
(Nick Cave)