kdevelop gdb commands

Im new to Kdevelop. Im trying to figure out where the gdb commands
come from when I launch gdb from kdevelop. Ive inherited this
project
from
a former employee and it seems that not only when gdb starts to run
it
excecutes a bunch of things, but the program Im trying to debug
crashes
and then it excecutes a bunch of other commands and finally stops and
I cannot figure out where all these commands (both before startup and
after crash) are coming from?

Secondarily, I want to add 3 commands to gdb before my program
starts excuting. Where do I add them? Or How do I add them so it
automatically starts up with those already executed? They are:


handle SIG64 nopass
handle SIG64 noprint
handle SIG64 nostop


Ive read the KDevelop manual and googled and cant seem to find these
answers so far.


Thanks for your help


.

Relevant Pages

  • kdevelop gdb commands
    ... Im trying to figure out where the gdb commands ... come from when I launch gdb from kdevelop. ... handle SIG64 noprint ...
    (comp.windows.x.kde)
  • Re: kdevelop gdb commands
    ... come from when I launch gdb from kdevelop. ... I cannot figure out where all these commands (both before startup and ... handle SIG64 noprint ... Ive read the KDevelop manual and googled and cant seem to find these ...
    (comp.os.linux.development.apps)
  • Re: kdevelop gdb commands
    ... come from when I launch gdb from kdevelop. ... I cannot figure out where all these commands (both before startup and ... handle SIG64 noprint ... Ive read the KDevelop manual and googled and cant seem to find these ...
    (comp.os.linux.development.apps)
  • GDB has problems with getting commands piped to STDIN
    ... I'm trying to pipe commands to gdb but I get the following messages: ... fgets to send commands and read the output they cause gdb to produce. ... To make sure this is not a PHP problem I already tested the following: ...
    (comp.os.linux.development.apps)
  • Re: generating stack dump in C++ application??
    ... Piping to an interactive program like gdb would not work because the pipe ... can't mimic the behavior of stdin that well. ... where commands will be a file containing the gdb commands, ... so there should be data on the stack. ...
    (comp.os.linux.development.system)