GDB Debugging Crash

abdrhmn — Tue, 27 Feb 2024 10:02:31 GMT

Hi,

I'm having a some problem to debug using Microsoft Visual Code with MCUXpresso extension. The error happens when I run debugging using JTAG/JLink.

Error is as below:

/mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-338_20211018_1634516203/src/gdb/gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 4064 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]

This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

/mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-338_20211018_1634516203/src/gdb/gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 4064 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]

I noticed it happens when the arm-none-eabi-gdb.exe memory usage exceeds 1.6GB-1.8GB of RAM. It can be monitor using task manager. I also found out it only happens when I run my code, I'm developing driver for iMX8ULP. By the way, it didn't happens if I use the example provided by NXP.

Please advice.

Re: GDB Debugging Crash

JorgeCas — Tue, 27 Feb 2024 23:42:27 GMT

Hello,

Could you please try with mentioned on this post?

It seems that is an error caused by a bad installation.

Best regards.

Re: GDB Debugging Crash

abdrhmn — Wed, 28 Feb 2024 06:57:47 GMT

Hi,

I already try the solutions that you mentioned. After reinstall I still observed the same issue.

Re: GDB Debugging Crash

JorgeCas — Wed, 28 Feb 2024 20:56:00 GMT

Hello,

Which J-link software do you have installed on your setup?

Did you check application note AN14120?

Best regards.

topic Re: GDB Debugging Crash in MCUXpresso for VSCode

GDB Debugging Crash

Re: GDB Debugging Crash

Re: GDB Debugging Crash

Re: GDB Debugging Crash