Lines Matching +refs:gdb +refs:stack +refs:buffer

782 You cannot portably "stack" cpp directives.  For example in the above
1126 either to see the stack trace of a core dump (very useful in a bug
1149     l  Context (loop) stack processing
1182 We'll use C<gdb> for our examples here; the principles will apply to
1190     gdb ./perl
1194     gdb ./perl core
1200     (gdb)
1245   (gdb) ptype PL_op
1265 heavy use of macros, and F<gdb> does not necessarily support macros
1266 (see later L</"gdb macro support">).  You'll have to substitute them
1282 =head2 gdb macro support
1284 Recent versions of F<gdb> have fairly good macro support, but in order
1303     (gdb) break Perl_pp_add
1310     (gdb) run -e '$y = "6XXXX"; $z = 2.3; $x = $y + $z'
1312 Lots of junk will go past as gdb reads in the relevant source files and
1317     (gdb) step
1319     (gdb)
1329 C<POPn> takes the SV from the top of the stack and obtains its NV
1331 function.  C<TOPs> takes the next SV from the top of the stack - yes,
1339     (gdb) step
1342     (gdb)
1346     (gdb) print Perl_sv_dump(sv)
1358     (gdb) finish
1370     (gdb) print Perl_op_dump(PL_op)
1388 =head2 Using gdb to look at specific parts of a program
1399 And in gdb do:
1401     (gdb) break Perl_pp_study
1410 =head2 Using gdb to look at what the parser/lexer are doing
1419 And in gdb:
1421     (gdb) break Perl_pp_study
1592 stack is a good sign of these.  Fixing these leaks is non-trivial,
1642 buffer overflow conditions, and is fast enough that you can easily
1981 A F<gdb> session on a threaded perl might look something like this:
1983     $ gdb ./perl
1984     (gdb) break Perl_pp_entereval
1985     (gdb) run -e'while (1) { eval q{\(1..3)} }'
1988     (gdb) call Perl_sv_mark_arenas(my_perl)
1989     (gdb) continue
1992     (gdb) call Perl_sv_sweep_arenas(my_perl)
1999     (gdb) 
2049 =head2 DDD over gdb
2051 Those debugging perl with the DDD frontend over gdb may find the
2081 Note: you can define up to 20 conversion shortcuts in the gdb section.
2086 (similar to what symbolic debuggers like gdb do).
2088 The backtrace returns the stack trace of the C call frames, with the