Disable gdb for release builds
-
@Ejok88 said in Disable gdb for release builds:
When I run my program in the release mode
Clarify what you mean by this: are you talking about compiling for Release vs Debug or are you talking about whether you press the Run vs Debug button to run the program from Creator? If you are only talking about how you compile then I cannot see that gdb would be involved in any shape or form.
-
-
-
@Ejok88 said in Disable gdb for release builds:
@JonB try to run a some program and then attach gdb to it (And you will see such messages in the application output panel):
I don't understand. You asked a question about "run my program in the release mode", and confirmed you click the Run button. No debugger is involved. You have not mentioned using a debugger, you have not mentioned attaching to running processes. You ask about the messages produced.
Now all of a sudden you seem to talk about "attaching gdb to a running process". Having never mentioned such before. Of course that will produce "attach" messages, Maybe someone else will understand what you are actually asking about, I do not.
-
@JonB I'm sorry, I probably didn't ask my question quite clearly.
I want to ask - how to eliminate the cause of this behavior? I mean:
- how to find and disable the source of these messages?
I explained that these messages are similar to gdb messages, so I'm trying to find where I can disable gdb in QtCreator.
I gave you an example of "attaching gdb to a running process" to explain how I understood where these messages come from.
-
@Ejok88
But if you "disable" gdb you won't be able to "attach" to running processes.
I don't think you can "disable" gdb, but you could always go to where you specify the path to it in your Settings and delete/make it nonsense there.
I cannot see how/why Creator would suddenly run gdb, or attach to any process, if all you do is Run an executable from there.
The messages look to me like some "hook" which monitors attaching/detaching to processes, maybe to debug them, maybe to "monitor" them. I don't know what is happening to cause that or where they come from.
Under Windows anything which produces "debug" output will appear in Creator's "debug" output window. It may not be anything in your code or anything in Qt code.
I don't know what application would be producing output of the formCurrent version :s IsWin11System: -1[PREVIEW] recv window msg, name:(Qt5QWindowIcon) hwd:(505ec) isvisiable(0) istopwnd(1) isTool(0) isPreview(0) pid:(6380)Given that it's misspelled, are you sure it's not your own code, or maybe some third-party (Qt?) library, which is outputting this?
Hmm, have you seen https://stackoverflow.com/questions/74938151/why-does-my-qt-creater-output-a-bunch-of-weird-messages-in-the-application-outpu and https://stackoverflow.com/questions/76613326/wierd-debug-output-qt-creator? Looks like those are same as you, and I don't think anyone knows where they come from :) Search the whole of Qt source code?
-
I encounter this problem as well. But I haven't got any solutions yet!
-
@Frank_Xiao It looks like you're running a debug build. Do you have same problem with release build?
-
@jsulm yes. no matter which mode I use, the information remains the same.
(btw, plz vote for me so that I can get 1 reputation score to send more replies without waiting for another 10 minutes)
-
@JonB you got any progress about this problem?
-
Actually, I think it might have nothing to do with Qt and its libraries. Maybe it's about the environment???
I am using Windows 11 Pro (and Windows 11 family before, still has the same problem), I have Visual Studio 2022 and Visual Studio Code installed, and I used to code and build with Visual Studio 2022 with the Qt extension. And, maybe, I encountered this problem after I build and run with VS2022 but I can't be sure if it's because of VS2022.
Has anyone used Visual Studio before to build and run Qt projects and encounter this problem?
@Ejok88 Did you do the same like me (using VS 2022)? -
@Frank_Xiao said in Disable gdb for release builds:
@JonB you got any progress about this problem?
It wasn't my problem! If you really want to know I suggested:
Search the whole of Qt source code?
