cs01 / cs01/gdbgui

Disables gdb's ability to set breakpoint on a file/function in a future shared library

Open
#238 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
10.4k
Forks
521
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
If we're trying to add a breakpoint, in a file/function which is part of a shared library that will be loaded once the program starts, gdb gives a prompt asking us if we want it to set the breakpoint upon loading of that library in the future. This works well.

Now with the .gdbinit, this prompt never appears. Instead I've to do a 'start' and the set the breakpoint.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
The prompt to set the breakpoint upon a future load of a shared library should appear

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Please complete the following information:**
* OS: Linux
* gdbgui version (`gdbgui -v`): latest
* gdb version (`gdb -v`):
* browser [e.g. chrome, safari]:
* python packages (`pip freeze`):

**Additional context**
https://stackoverflow.com/questions/100444/how-to-set-breakpoints-on-future-shared-libraries-with-a-command-flag

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.