Tracing on Windows - "failed to execute ... (2)"

[io.github.apitrace at io7m.com]

Hi.

I'm trying to debug an OpenGL program written in Java. The program
comes with a tiny frontend executable that simply sets up the Java
classpath and forks a JVM to run the program. The executable was
produced with launch4j (http://launch4j.sourceforge.net).

I'm using the latest apitrace binaries available on the site
(http://people.freedesktop.org/~jrfonseca/apitrace/apitrace-msvc-latest.7z).

I get the following error when trying to trace the program:

  > apitrace trace --verbose viewer.exe
  info: did not find C:\Users\testing\Desktop\apitrace-msvc\x86\bin\..\wrappers\RelWithDebInfo\opengl32.dll
  info: found C:\Users\testing\Desktop\apitrace-msvc\x86\bin\..\wrappers\opengl32.dll
  inject: C:\Users\testing\Desktop\apitrace-msvc\x86\bin\..\wrappers\opengl32.dll viewer.exe
  error: failed to execute viewer.exe (2)

I've tried the x64 version but receive the same error.

Any idea how I can get some better error reporting out of it?

Some info that may be relevant: The system's JVM is a 64-bit executable:

  > java -version
  java version "1.8.0_20"
  Java(TM) SE Runtime Environment (build 1.8.0_20-b26)
  Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode)

... but I believe viewer.exe may be 32-bit. Could this have any effect
on apitrace?

M