-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
gdb main thread is bloocking ... #55
Comments
Hi, thank you for your feedback. Can you provide this informations?
|
@rohanrhu Hi. My OS is : I've found that the moment I load executable such as mariadbd(195M) or mysqld(662M), this warning will often pop out But if I load light-weight program such as postgres(29M) or my little custom program, I don't see this warning and Step over/step into is fast enough. So the problem seems to be why loading a big debug-version program has such issue ? |
Thank youu @baiwfg2 All of GF functions are working on GDB's main thread so something must be taking long time for big applications like MariaDB and MySQL contexts. There are two things:
For example ProcessManager rendering is well-optimized but SourceTree is not optimized as well as ProcessManager. Things I will improve:
But do you feel any freezing in UI for each step? I debug some big applications like Godot Engine and I never felt like frontend is freezing or an annoying blocking main thread warning for softwares I debugged but SourceTree and other components must render like ProcessManager's way. So it is something I will improve as next thing to do. Also I must test MariaDB and improve things that take long time in backend. MySQL is known as a bit memory hungry, it must have so many variables in each context and resolving them in backend (to show in frontend) must be taking some long time. I will improve them to a way that is more iteration-ish. The most important question for now is: |
not freezing for each step. Roughly frequent |
Oh good.. I was thinking about SourceTree but then it is good as I thought. At least it has some other optimizations rather than rendering optimizations. Then I will look at backend and optimize things for huge codebases. A MariaDB developer contacted me before and I improved things and debugged MariaDB I remember it was good but I will debug it again first and improve the performance for huge codebases and I will test on a low-end CPU. Btw could you give your hardware details? |
Actually I start a virtual fedora machine with virtualbox on my windows 10(4 CPUs, 24G RAM, HDD disk),. The virtual machine is equipped with 2 CPUs, 5G RAM. Before I start GF,
After I start GF,
Then I open browser and attach mariadbd process, quickly the blocking information is popped out... |
Thank you so much @baiwfg2 😊 I will fix it soon in next release. |
Thanks for making gdb so convenient. I've met with two problems.
One is when I'm debugging mariadbd program whose binary size is 195M, but show "gdb main thread is bloocking". I don't know what it means
another problem is that when I step over or step into, it's really slower than using gdb on the commandline. Can it be faster ?
The text was updated successfully, but these errors were encountered: