Hello there. I'm trying to run Mesen-X inside my build process, which worked before wi

Here is a link to my container's Dockerfile: <a href="https://github.com/empathicqubit

PR <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id=

Running Mesen-X headlessly with xvfb-run about mesen-x HOT 5 CLOSED

empathicqubit commented on August 27, 2024

Running Mesen-X headlessly with xvfb-run

from mesen-x.

Comments (5)

empathicqubit commented on August 27, 2024

Here is a link to my container's Dockerfile: https://github.com/empathicqubit/vscode-cc65-debugger/blob/master/docker/Dockerfile

from mesen-x.

empathicqubit commented on August 27, 2024

I think ideally xvfb would not be necessary at all, but that's a different issue.

from mesen-x.

empathicqubit commented on August 27, 2024

Possibly similar issue? https://trac.ffmpeg.org/ticket/1738

from mesen-x.

empathicqubit commented on August 27, 2024

Upgrading Mono fixes that specific issue, but now I'm sorting through a native code exception. I think I'm okay with updating Mono since there is an official path for that. Updating libc is impossible, however. ~~Please look at the above PR for the Github Actions script when you get the chance.~~

This is as far as I've gotten using Xvfb with these changes. The test still works locally.

        Starting Mesen xvfb-run ["-a","mono","/__w/vscode-cc65-debugger/vscode-cc65-debugger/src/__tests__/mesendir/Mesen.exe","--testrunner","/__w/vscode-cc65-debugger/vscode-cc65-debugger/src/../dist/mesen/mesen_binary_monitor.lua","/__w/vscode-cc65-debugger/vscode-cc65-debugger/src/__tests__/simple-project/program.nes"]
  
        at MesenGrip.autostart (src/dbg/mesen-grip.ts:49:21)
  
      console.log
        Could not set X locale modifiers
  
        at Socket.<anonymous> (src/__tests__/test-shared.ts:79:80)
  
      console.log
        
        =================================================================
        	Native Crash Reporting
        =================================================================
        Got a SIGSEGV while executing native code. This usually indicates
        a fatal error in the mono runtime or one of the native libraries 
        used by your application.
        =================================================================
  
        at Socket.<anonymous> (src/__tests__/test-shared.ts:79:80)
  
      console.log
        Aborted (core dumped)
  
        at Socket.<anonymous> (src/__tests__/test-shared.ts:79:80)