> > now whether gdb should let me print "pow(run.m*run.dr, 2)" or not, that's
> > gdb segfaulting. a debugger should _NOT_ segfault, under any
> > circumstances.
>
> Unless, there is a hardware problem, esp. memory, gdb will stress out
> your memory more than most apps. Do a kernel compile work
>
> now whether gdb should let me print "pow(run.m*run.dr, 2)" or not, that's
> gdb segfaulting. a debugger should _NOT_ segfault, under any
> circumstances.
Unless, there is a hardware problem, esp. memory, gdb will stress out
your memory more than most apps. Do a kernel compile work fine ?
H
On Mon, Sep 18, 2000 at 12:35:03PM -0700, Jakob 'sparky' Kaivo wrote:
> Peter Jay Salzman <[EMAIL PROTECTED]> writes:
> >
> > contact FSF or debian?
>
> bug-gdb@gnu.org
And also "info gdb". There's a long section on how to report bugs.
Cheers,
Chris
--
It is much easier to be critical than t
Peter Jay Salzman <[EMAIL PROTECTED]> writes:
> hello all,
>
> i'm debugging a c++ program, and found something very distressing:
>
> % gdb wellspring core
> GNU gdb 19990928
> (warranty snipped)
> This GDB was configured as "i686-pc-linux-gnu"...
> Core was generat
4 matches
Mail list logo
