Sysprogs forums › Forums › VisualGDB › Get rid of COM console
- This topic has 3 replies, 2 voices, and was last updated 3 years, 11 months ago by support.
-
AuthorPosts
-
December 8, 2020 at 07:15 #29637hopperplParticipant
So, I made the mistake of trying to use “Open Serial Terminal”.
While the feature works, I have no idea how do disable it. VisualGDB is constantly hogging that COM port. Yes, I can disconnect it, yes I can close the window. But VisualGDB constantly reconnects to it with every new debug session. I don’t want that, I said disconnect. That is a permanent decision, neither a suggestion nor a temporary idea. Disconnect. Stay disconnected. And no I don’t want to perform a 10-page check list to get everything ready for a new debug session.
Why would I need that? Well, some other program needs that COM port. And VisualGDB blocks that COM port access. I disconnect, I close the COM window, I restart the debug session and that annoying COM window is back open again and connection. That’s a 10/10 annoyance!
So, how do I get rid of the constant terminal connection?
And actually, this is a huge annoyance overall. When I decide to close a window, that window is ordered to stay closed. I don’t want VisualGDB to reopen windows when I start a new debug session. I waste hours with closing windows that VisualGDB opens without any authorization. “Live Watch”, “Hardware Registers”. “VisualGDB Output”. They all reopen all the time.
And yes, I’m extremely annoyed by this!
December 8, 2020 at 08:29 #29639supportKeymasterHi,
Unfortunately, we were not able to reproduce the problem based on the description you provided.
In order for us to diagnose it further, please provide a clear description of steps we could follow on our side to reproduce the issue, according to our problem reporting guidelines.
December 8, 2020 at 09:23 #29640hopperplParticipantseriously? it can’t be any easier
- debug any program
- go to the serial console window (COM5 in my case)
- click Disconnect
- close the Serial Console tab window
- click Debug > Restart (or Shift+Ctrl+F5)
- now, the serial console window is back, and it reconnects automatically
the same applies to all other VisualGDB windows. Close. Restart Debug Session (or Shift+Ctrl+F5), all return opened.
The same problem also occurs with the “Live Watch” or “Hardware Register” tab window of VisualGDB. It’s any window of VisualGDB. Just choose one. Any. I can close all tab windows. All of them. While debugging. All closed, nothing opened. Restart the debug session, and all VisualGDB, and only VisualGDB tab windows get all reopened.
No extensions/addons installed (except VisualGDB). Visual Studio 2019, 16.8.2 (Release)
Visual Studio is working fine, its own tab windows I can close and open and rearrange, and the information is kept between debug sessions.
December 8, 2020 at 09:33 #29641supportKeymasterThanks, we have added it to the backlog and will try to address it in one of the next releases.
-
AuthorPosts
- You must be logged in to reply to this topic.