Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ChatDBG Success Stories #53

Open
khlevin opened this issue Nov 12, 2024 · 1 comment
Open

ChatDBG Success Stories #53

khlevin opened this issue Nov 12, 2024 · 1 comment

Comments

@khlevin
Copy link
Contributor

khlevin commented Nov 12, 2024

We want to hear how you use ChatDBG to debug, how it's worked for you or helped you on your various projects!
Whether it's finding tricky bugs, helping to speed up your workflow, or just making the programming process easier as a whole, let us know how ChatDBG has been able to help you.
Tell us all about your very own ChatDBG success stories right here!

@CodemanRichard
Copy link

I think you can consider integrating data flow to the process of trace fetching. In most cases the variable related to the root cause is not even included in the prompt sent to GPT and GPT is still not smart enough to use pdb to find this problem variable.
Anyway I like your work :) If the program runs faster, I would definitely choose ChatDBG as the upward substitution of pdb.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants