Debugger was unable to continue the process

RE: Debugger was unable to continue the process

dejans — Thu, 27 Jun 2024 09:21:52 GMT

Hi,

I can only recommend caution in your case. Launching multiple debug sessions on the same (multi-core device) board will be needed and required.

Best regards,
Dejan

RE: Debugger was unable to continue the process

slight — Wed, 26 Jun 2024 15:36:56 GMT

Seems like that should be something that should be prevented given how easy it is to accidentally start a 2nd debug session and the confusion and possible misoperation that happens if you do.

RE: Debugger was unable to continue the process

dejans — Wed, 26 Jun 2024 08:50:36 GMT

Hi,

The possibility of using multiple debug session is inherent to VS Code and we do not impose any limit on that. However, debugging the same device multiple time is not recommended. Multiple debug sessions should be used on different devices or for debugging multi-core SoC (one debugging session per core).

Best regards,
Dejan

RE: Debugger was unable to continue the process

slight — Tue, 25 Jun 2024 13:25:28 GMT

No, I am using the DK. Latest Visual Studio Code from a few weeks ago.

RE: Debugger was unable to continue the process

dejans — Tue, 25 Jun 2024 09:22:08 GMT

Hi,

[quote user="slight"]The datasheet for the part I am using doesn't indicate it is multi-core.[/quote]

Do you have a custom board with nrf52840?

[quote user="slight"]Therefore, in my mind, the development system should not be allowing multiple (possibly conflicting) debug sessions.[/quote]

Which debugging tool and debugger do you use?

Best regards,
Dejan

RE: Debugger was unable to continue the process

slight — Mon, 24 Jun 2024 15:59:31 GMT

The datasheet for the part I am using doesn't indicate it is multi-core. Therefore, in my mind, the development system should not be allowing multiple (possibly conflicting) debug sessions.

RE: Debugger was unable to continue the process

dejans — Mon, 24 Jun 2024 09:46:35 GMT

Hi,

When using multicore SoC, you can use 2 separate debug sessions, one for each of the cores. You can find more information on how to debug application and debugging multi-core SoC in the documentation.

Best regards,
Dejan

RE: Debugger was unable to continue the process

slight — Fri, 21 Jun 2024 14:39:42 GMT

If I manage to come up with something, I will repost, but it could take considerable time. In general, I've noticed that switching back and forth between build configurations might be a trigger. Possibly opening a different project while one is still being debugged? Also, I've noticed it is possible to get more than one debug session going at the same time. I don't know if that's an intentional feature, but it sure doesn't work very well. Probably best if someone more familiar with the development system plays around with it as I'm just starting out with Nordic.

RE: Debugger was unable to continue the process

dejans — Fri, 21 Jun 2024 08:32:16 GMT

Hi slight ,

If you think that there might be a bug in the development system, please open a new ticket, describe the issue and provide steps for reliably reproducing it.

Best regards,
Dejan

RE: Debugger was unable to continue the process

slight — Wed, 19 Jun 2024 21:52:19 GMT

I've been playing around with this for a while now and discovered that if I deleted all my breakpoints, it stopped happening. Seems the development system has some sort of bug with regard to where it is inserting breakpoints in the actual code. Perhaps when the source changes it gets confused and puts the breakpoint in a funny place in memory.

RE: Debugger was unable to continue the process

slight — Wed, 19 Jun 2024 21:28:59 GMT

I am seeing a similar problem with my application. It is a relatively simple application and I am stuck right now unable to debug. I am just running it on the 52840 DK. Previously I managed to get it to work again by shutting down Visual Studio Code and restarting, then "tweaking" my code to get it to recompile. But, no luck now. Very frustrating.

RE: Debugger was unable to continue the process

dejans — Wed, 13 Mar 2024 09:09:46 GMT

Hi,

[quote user="dejans"]Which simple sample have you tried to test with? Did you see the same behavior as with your custom application?[/quote]

Best regards,
Dejan

RE: Debugger was unable to continue the process

Kyle — Tue, 12 Mar 2024 15:34:02 GMT

When the pop-up appears when I start the debugger, it will work regardless of whether I click "Yes" or "No".

When the pop-up doesn't appear, and the debugger just starts immediately, it fails with the originally posted error.

I cannot find any correlation between my actions or changes, and whether the pop-up appears or not. It seems to be random.

RE: Debugger was unable to continue the process

dejans — Tue, 12 Mar 2024 10:42:42 GMT

Hi,

What happens if you choose "Yes" when informed that "monitor mode is for evaluation purposes only"?

Which simple sample have you tried to test with? Did you see the same behavior as with your custom application?

Best regards,
Dejan

RE: Debugger was unable to continue the process

Kyle — Mon, 11 Mar 2024 22:16:03 GMT

When the issue occurs, it doesn't offer the prompt. It just immediately crashes with the given error.

RE: Debugger was unable to continue the process

hmolesworth — Mon, 11 Mar 2024 22:15:04 GMT

Debugging a BLE application always used to require Monitor Mode active to avoid crashes when using breakpoints or single-stepping; maybe try "Yes" at the prompt ..

RE: Debugger was unable to continue the process

Kyle — Mon, 11 Mar 2024 19:28:21 GMT

No, it's not alternating. It seems more like it fails for a period of time (regardless of how many times I try to use it during that time window), then resumes working again.

One association I've noted is that this issue started occurring around the same time that I started getting pop-up notifications every time I start the debugger, informing me that "monitor mode is for evaluation purposes only", and asking me if I want to enable it (I select "No").

I do not recall making any configuration changes that caused this pop-up to start showing, and it's unclear if it's related to the issue.

RE: Debugger was unable to continue the process

dejans — Mon, 11 Mar 2024 10:32:36 GMT

Hi,

Which application did you use for testing?

[quote user="JordanK"]It's definitely not the board or the firmware. I ran it once, it worked fine. Debugged again, it threw the error. Debugged again, it worked fine. No changes to the devicetree, board config, or firmware in between.[/quote]

Can you confirm that debugging works every other time you try (i.e. alternates between working and not working)?

Do you see the same alternating behavior (working and non-working) with both your testing application and your custom application?

Best regards,
Dejan

RE: Debugger was unable to continue the process

Kyle — Mon, 11 Mar 2024 00:06:35 GMT

It's definitely not the board or the firmware. I ran it once, it worked fine. Debugged again, it threw the error. Debugged again, it worked fine. No changes to the devicetree, board config, or firmware in between.

RE: Debugger was unable to continue the process

dejans — Thu, 07 Mar 2024 14:08:38 GMT

Hi,

This seems to be a good approach to start with simple application on the DK board.

Best regards,
Dejan

RE: Debugger was unable to continue the process

Kyle — Wed, 06 Mar 2024 15:03:45 GMT

Hi Dejans,

It's a custom board based on the nRF5340DK board definition. This is occurring in a custom, large application. I'll try it with a simple sample and a standard board as well and see if it occurs.

RE: Debugger was unable to continue the process

dejans — Wed, 06 Mar 2024 14:48:03 GMT

Hi,

Which board do you use?

Which application sample do you use?

Best regards,
Dejan