By default, we ignore the content of ~/.gdbinit.
We do this because we had several users who were not able to start the integrated debugging because they had things in their .gdbinit that broke everything. Since we have no control over what people put in their .gdbinit, and GDB makes not restrictions on it either, we launch GDB with the -nx option to tell it to ignore it.
You can override this behavior by setting up a custom GDB configuration. Debug > Debugger Options... > Configurations >
- . You can then point SlickEdit to the GDB executable of your choice and then specify in the arguments -x ~/.gdbinit to force it to load your settings from gdbinit. Check the
- Default native debugging configuration checkbox when you are done so that SlickEdit uses your GDB configuration by default when debugging local applications.
Also, FWIW, we do plan on adding a Debug Signals tool window in a future release to simplify handling and configuration of signal handling. We realize that currently it is rather tedious in the cases where GDB's default behavior is not adequate.