Re: Which editor for C/C++ programming, and more...

In message <>, Cory Wa
tson writes:

>Plus, you never know when a binary may start segfaulting, and if you've
>stripped it, gdb isn't going to help you in submitting a bug report or fix
>a problem.

Recompile the seg faulting program with debugging symbols, reproducing the bug.

If you can't reproduce the bug, how can anybody else?

It's better to run optimized binaries normally and when you run into programs
that seg fault, recompile them without *any* optimization flags and -g.  Then
your backtrace will be the most enlightening.


John GOTTS <>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]