Kai Henningsen wrote:
> A classical memory corruption bug, and like most late-effect bugs hell to
> find without some sort of support for poking around in the actual program
> state.
Agreed. My usual debugging procedure is as follows:
1. try to reproduce the problem
2. make an educated gue
[EMAIL PROTECTED] (Ingo Molnar) wrote on 05.09.00 in
<[EMAIL PROTECTED]>:
> On Tue, 5 Sep 2000, Andi Kleen wrote:
>
> > I don't really believe that. It is as easy to add a silly NULL pointer
> > check based on a oops as it is after a debugging session (and it is
> > even likely you chose the si
[EMAIL PROTECTED] (David S. Miller) wrote on 05.09.00 in
<[EMAIL PROTECTED]>:
> I don't want this
> to start happening, and automated debugging/profiling tools tend to
> encourage people to operate in such a way.
Somehow I suddenly get the impression we're talking past each others.
Since w
3 matches
Mail list logo
