Skip to main content



      Home
Home » Language IDEs » C / C++ IDE (CDT) » show view memory monitors or memory browser when debug termination
show view memory monitors or memory browser when debug termination [message #1842508] Mon, 21 June 2021 21:30 Go to next message
Eclipse UserFriend
When debugging, check the memory variable value, and the adjustment automatically terminates. What is the reason?

As shown in the figure, 1624325058(1).jpg, 2.jpg, 3.jpp sequence, when you fill in the address to view the memory value, the debug will automatically terminate。

Ask the cause of the problem, thank you

  • Attachment: 1624325058(1).jpg
    (Size: 107.99KB, Downloaded 86 times)
  • Attachment: 2.jpg
    (Size: 109.84KB, Downloaded 77 times)
  • Attachment: 3.jpg
    (Size: 112.89KB, Downloaded 76 times)
Re: show view memory monitors or memory browser when debug termination [message #1844213 is a reply to message #1842508] Mon, 06 September 2021 08:34 Go to previous messageGo to next message
Eclipse UserFriend
I have exactly the same problem. Have you found a solution?
Re: show view memory monitors or memory browser when debug termination [message #1844237 is a reply to message #1844213] Mon, 06 September 2021 22:03 Go to previous messageGo to next message
Eclipse UserFriend
The program terminated with a negative exit code.
In Windows this usually indicates a Windows error code.

Convert it to a 32-bit hex value and do a web search for it.
Re: show view memory monitors or memory browser when debug termination [message #1844249 is a reply to message #1844237] Tue, 07 September 2021 03:15 Go to previous messageGo to next message
Eclipse UserFriend
I'm on Linux and the exit code is always 0. The strange thing is that if I don't use the memory browser but I use the console debugger directly (so directly the gdb) to view the memory, I can continue debugging without the processes ending.
Re: show view memory monitors or memory browser when debug termination [message #1844251 is a reply to message #1844249] Tue, 07 September 2021 04:14 Go to previous messageGo to next message
Eclipse UserFriend
The OP had a negative exit code and was running under Windows.
You said you had "exactly the same problem".
And only now begin telling us how it's different

You should try to be more accurate.
We're not mind readers.

[Updated on: Tue, 07 September 2021 04:24] by Moderator

Re: show view memory monitors or memory browser when debug termination [message #1844260 is a reply to message #1844251] Tue, 07 September 2021 05:38 Go to previous messageGo to next message
Eclipse UserFriend
You're right, I apologize for the lack of accuracy. However, what happens is the same thing, I start debugging and I can continue to do it without problems until I try to see the memory. As soon as I do this the process ends.

[Updated on: Tue, 07 September 2021 05:40] by Moderator

Re: show view memory monitors or memory browser when debug termination [message #1844267 is a reply to message #1844260] Tue, 07 September 2021 11:39 Go to previous messageGo to next message
Eclipse UserFriend
I've never experienced the problem but it may be a bug.
I assume the OP fixed the problem on his end.
Would be nice to know what caused it.
Might be related to yours.

You could try filing a bug report and maybe get someone
to dig into it for you.
Re: show view memory monitors or memory browser when debug termination [message #1844274 is a reply to message #1844267] Tue, 07 September 2021 14:41 Go to previous messageGo to next message
Eclipse UserFriend
The OP wants to look around an automatic variable's address. The automatic variable is in the function's stack. There is little to gain from printing the address,
as it is probably different on different calls to the function.

The bulk memory access may extend out of the legal address range and it can raise a memory management exception which kills the process.
Re: show view memory monitors or memory browser when debug termination [message #1844634 is a reply to message #1844274] Sun, 19 September 2021 03:40 Go to previous message
Eclipse UserFriend
I solved downgrading the gdb from 10.2 to 8.3. Now everything works perfectly.

[Updated on: Sun, 19 September 2021 03:53] by Moderator

Previous Topic:2021-09 - no path to "make"
Next Topic:Windows views - how to keep them organized ?
Goto Forum:
  


Current Time: Sun Jul 13 07:03:43 EDT 2025

Powered by FUDForum. Page generated in 0.04064 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top