Gallopsled / Gallopsled/pwntools

gdb.debug stops at every breakpoint, running slow

Open
#2,433 5 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
Python
Stars
13.7k
Forks
1.9k
Avg merge
6d 23h
Merged PRs (30d)
3

Description

Is it intended for the newly opened gdb terminal to keep displaying the "Breakpoint 1" message when it hits a breakpoint? How do i disable this or better yet, how do I gdb.debug without the new terminal opening as I just want it to print the values purely based off my python script?

When I ran gdb.debug a few months back, the same script managed to run through without any issues and without any delay. After the update of rpyc or gdb or pwntools (im not sure which is the cause), it would start displaying the breakpoints continuously, would run slowly, and may even be unable to run properly.

![image](https://github.com/user-attachments/assets/371e784d-19fd-4379-a3f2-e274b6616743)

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by reproducing the behavior through the gdb.debug entry point and compare the current breakpoint and terminal behavior with the earlier workflow described in the issue. Done means identifying the regression and confirming that debugging no longer stops repeatedly or opens an unwanted terminal.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.