Eclipse Community Forums: C / C++ IDE (CDT) » show view memory monitors or memory browser when debug termination

Help

Home

Home » Language IDEs » C / C++ IDE (CDT) » show view memory monitors or memory browser when debug termination

Show: Today's Messages :: Show Polls :: Message Navigator

show view memory monitors or memory browser when debug termination [message #1842508]

Tue, 22 June 2021 01:30

yong wang

Messages: 1
Registered: June 2021

Junior Member

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 42 times)
Attachment: 2.jpg
(Size: 109.84KB, Downloaded 34 times)
Attachment: 3.jpg
(Size: 112.89KB, Downloaded 35 times)

Report message to a moderator

Re: show view memory monitors or memory browser when debug termination [message #1844213 is a reply to message #1842508]

Mon, 06 September 2021 12:34

Fabio Cavallo

Messages: 4
Registered: September 2021

Junior Member

I have exactly the same problem. Have you found a solution?

Report message to a moderator

Re: show view memory monitors or memory browser when debug termination [message #1844237 is a reply to message #1844213]

Tue, 07 September 2021 02:03

David Vavra

Messages: 1430
Registered: October 2012

Senior Member

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.

Report message to a moderator

Re: show view memory monitors or memory browser when debug termination [message #1844249 is a reply to message #1844237]

Tue, 07 September 2021 07:15

Fabio Cavallo

Messages: 4
Registered: September 2021

Junior Member

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.

Report message to a moderator

Re: show view memory monitors or memory browser when debug termination [message #1844251 is a reply to message #1844249]

Tue, 07 September 2021 08:14

David Vavra

Messages: 1430
Registered: October 2012

Senior Member

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 08:24]

Report message to a moderator

Re: show view memory monitors or memory browser when debug termination [message #1844260 is a reply to message #1844251]

Tue, 07 September 2021 09:38

Fabio Cavallo

Messages: 4
Registered: September 2021

Junior Member

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 09:40]

Report message to a moderator

Re: show view memory monitors or memory browser when debug termination [message #1844267 is a reply to message #1844260]

Tue, 07 September 2021 15:39

David Vavra

Messages: 1430
Registered: October 2012

Senior Member

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.

Report message to a moderator

Re: show view memory monitors or memory browser when debug termination [message #1844274 is a reply to message #1844267]

Tue, 07 September 2021 18:41

Tauno Voipio

Messages: 722
Registered: August 2014

Senior Member

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.

--

Tauno Voipio

Report message to a moderator