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 generated by `./wellspring'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libstdc++-libc6.1-2.so.3...done.
Reading symbols from /lib/libm.so.6...done.
Reading symbols from /lib/libc.so.6...done.
Reading symbols from /lib/ld-linux.so.2...done.
#0 0x804ced8 in GetPotential ([EMAIL PROTECTED], V=0x8053028,
wf=0x805b588)
at functions.cc:51
51 V[j] = -4.0L*PI*G*pow(run.m*run.dr,
2.0L)*(run.sum1[j] + run.sum2[j]);
(gdb) p run.m*run.dr
$1 = 0.013599479808447117947299662577692603
(gdb) p pow(run.m*run.dr, 2)
Segmentation fault (core dumped)
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.
i feel gdb is the most important program besides the linux kernel and the
C/C++ compilers. this should be fixed. what should i do?
contact FSF or debian?
pete
---------------------------------------------------------------- linux
One world, one web, one program. -- Microsoft Ad Campaign _
Ein Volk, ein Reich, ein Fuhrer. -- Nazi Ad Campaign ._.
<=>+/\/-=Prevent world domination, Install Linux today!=-\/\+<=> /v\
website coming soon as I get DSL [EMAIL PROTECTED] // \\
---------------------------------------------------------------- ^^ ^^
The best way to accelerate a win95 system is at 9.81 m/s^2 rules
