New Error Trying to Debug from VS Code

Technical Support
, , , ,
1

This has been working for over a year, until this week. The build/debug process almost completes but fails to start debugging. Any suggestions welcome.

Starting:
“ssh” -T -q -p 22 -i .conf/id_rsa -o StrictHostKeyChecking=no -o “UserKnownHostsFile /dev/null” torizon@192.168.1.181 “~/vsdbg/vsdbg --interpreter=vscode”

Exception:
Error from pipe program ‘ssh’: Process terminated. Couldn’t find a valid ICU package installed on the system. Please install libicu (or icu-libs) using your package manager and try again. Alternatively you can set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support. Please see Globalization config settings - .NET | Microsoft Learn for more information.

Error from pipe program ‘ssh’: at System.Environment.FailFast(System.String)
Error from pipe program ‘ssh’: at System.Globalization.GlobalizationMode+Settings…cctor()
Error from pipe program ‘ssh’: at System.Globalization.CultureData.CreateCultureWithInvariantData()
Error from pipe program ‘ssh’: at System.Globalization.CultureData.get_Invariant()
Error from pipe program ‘ssh’: at System.Globalization.CultureInfo…cctor()
Error from pipe program ‘ssh’: at System.Globalization.CultureInfo.get_InvariantCulture()
Error from pipe program ‘ssh’: at System.Globalization.NumberFormatInfo.get_InvariantInfo()
Error from pipe program ‘ssh’: at System.Reflection.AssemblyNameParser.ParseVersion(System.String)
Error from pipe program ‘ssh’: at System.Reflection.AssemblyNameParser.Parse()
Error from pipe program ‘ssh’: at System.Reflection.AssemblyName.ParseAsAssemblySpec(Char*, Void*)
The pipe program ‘ssh’ exited unexpectedly with code 255.

Tried setting this:
PropertyGroup
InvariantGlobalization
true
InvariantGlobalization
PropertyGroup

This is a blazor app running in docker on a verdin am62.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello! I’m happy to help you troubleshoot this issue.

The error you are seeing—specifically, “Couldn’t find a valid ICU package installed on the system. Please install libicu (or icu-libs) using your package manager and try again”—indicates the required ICU (International Components for Unicode) library is missing on your Torizon device. This is a dependency for .NET debugging tools like vsdbg. Sometimes, after updates or changes to the device or its software, these dependencies may be absent or removed.

Steps to resolve:

  1. Connect via SSH Manually:
    Before proceeding, ensure you can SSH into your board:

    ssh torizon@192.168.1.181

    Password is usually torizon (Guide).

  2. Check for ICU Library:
    Once connected, check if libicu or icu-libs is installed:

    dpkg -l | grep icu

    On Torizon, which uses Debian-based containers, you can typically install ICU like this:

    sudo apt-get update
sudo apt-get install -y libicu-dev

  3. If Using Docker Containers:
    If your debug environment is inside a container, ensure that your Docker image installs libicu:

    RUN apt-get update && apt-get install -y libicu-dev

    Then rebuild and redeploy your container.

  4. Configuration Alternative:
    If your application doesn’t require globalization features, you may set .NET’s invariant mode to bypass ICU, though this is just a workaround:

    • Add an environment variable before launching:
      export DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1
    • Or configure this in your application’s runtime configuration.

  5. Logs and Status:
    If you continue to have issues, check the SSH service status and vsdbg logs:

    systemctl status sshd.socket
journalctl -u sshd*

    (SSH Troubleshooting)

Summary:
Most likely, installing the ICU libraries (sudo apt-get install -y libicu-dev) on your Torizon device or in your Docker container will resolve the issue. If you are running code in a read-only or minimal container, ensure ICU is present by updating your Dockerfile.

Let me know if this fixes your debugging startup, or if you need guidance tailored to your exact build/deploy flow!

Best regards,
Toradex AI Assistant.

(SSH guide)
(SSH troubleshooting)

3

Hi @gfrankel

Sorry you are having trouble. I’ll try to reproduce this.

What version of Torizon and the IDE extension are you running?

Can you reproduce this with a newly created project?

And just to confirm you are on a verdin-am62 (not 64) module correct?
Drew

4

Hi Drew, thank you!

Torizon IDE Extension: 3.0.4
Docker IDE Extension: 2.0.0
verdin-am62 is correct

I will try it with a new project.

5

Hi @gfrrankel

My best guess is that you are being affected by the recent change that Microsoft made to the docker/container-tools extension. Since you are running the 2.0.0 version of the Docker extension, I suspect this is the root cause. See this post for more details. Basically, unless you want to switch to the prerelease version of the IDE extension you will need to downgrade the Docker extension for the time being.

I just verified this in my environment with the release version of the IDE extension. Please let me know how it goes.

Drew

6

I am able to debug with VS code when running the sample .net blazor project on our device.

7

Hi @gfrrankel

That’s good. Have you had a chance to test with the either the prerelease version of the IDE extension or the older version of the Docker extension? Hopefully that will unblock you on your actual project.

Drew

8

Hi Drew, I am able to debug using the older Docker extension, thanks for the help!

9

That’s great. At least it’s a known issue. For now I’ll consider this solution resolved. When the next version of the IDE extension is out you should be able to update to the newer Docker extension. Please let me know if you have further issues at that time.

Drew