Cabbage Logo
Back to Cabbage Site

Windows 10 slugs (resolved)

#21

Here is a link to a debug build of Cabbage Studio:
https://dl.dropboxusercontent.com/u/11301894/CabbageStudio.zip
You should replace CabbageStudio.exe in your Cabbage dir with the one in this zip file. Then download the following, unless you already have gdb installed(it comes with mingw).
ftp://ftp.equation.com/gdb/snapshot/32/gdb.exe
Place that file into the same directory as CabbageStudio.exe. The open the command line, enter the following command and hit enter:

cd "C:\Program Files (x86)\Cabbage32"

Then this:

gdb CabbageStudio.exe

gdb will then load Cabbage Studio. Next type ‘run’ and see what happens. I’m hoping at this point we get some useful information about why it is not working!

#22

inexplicably, now it runs properly!

here’s the output from gdb:

C:\Program Files (x86)\Cabbage32>gdb CabbageStudio.exe
GNU gdb (GDB) 7.5
Copyright © 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
This GDB was configured as “i686-pc-mingw32”.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/…
Reading symbols from C:\Program Files (x86)\Cabbage32\CabbageStudio.exe…done.
(gdb) run
Starting program: C:\Program Files (x86)\Cabbage32\CabbageStudio.exe
[New Thread 3624.0x824]
[New Thread 3624.0x17bc]
[New Thread 3624.0x17c4]
[New Thread 3624.0x17c0]
[New Thread 3624.0x17c8]
[New Thread 3624.0x7fc]
[New Thread 3624.0xa88]
[New Thread 3624.0xbec]
[New Thread 3624.0xbf0]
[New Thread 3624.0x990]
[New Thread 3624.0x17f8]
[New Thread 3624.0x17fc]
[New Thread 3624.0x17f0]
[New Thread 3624.0xfb8]
[New Thread 3624.0xf74]
[New Thread 3624.0x1cec]
[New Thread 3624.0x714]
[New Thread 3624.0x164c]
[New Thread 3624.0x111c]
[New Thread 3624.0x1ae4]
[New Thread 3624.0x1030]
[New Thread 3624.0x17e4]
warning:

Cabbage opcode plugins are located at:C:\Program Files (x86)\CabbageStudio32;C:\Program Files (x86)\Cabbage32

warning: compiled Ok

warning: ======EDITOR DECONSTRCUTOR=========

warning: about to cleanup Csound

warning: Csound cleaned up

[Inferior 1 (process 3624) exited normally]
(gdb)

launching normally also works.

#23

Ok, that’s something at least. What bothers me is the line about Cabbage opcode plugins. C:\Program Files (x86)\CabbageStudio32 doesn’t exist. This could be what is causing issues for Iain too. Let me investigate further…

#24

Can you try this one. Just rename the one that works and drop this one in in its place:
https://dl.dropboxusercontent.com/u/11301894/CabbageStudio.zip
It is a release build, but I just want to see if it works. Thanks for your patience!

#25

no, it quits back to windows again…

but here’s gdb’s output:

Reading symbols from C:\Program Files (x86)\Cabbage32\CabbageStudio.exe…done.
(gdb) run
Starting program: C:\Program Files (x86)\Cabbage32\CabbageStudio.exe
[New Thread 7464.0x14d4]
[New Thread 7464.0x1d24]
[New Thread 7464.0x1e34]
[New Thread 7464.0x1f7c]

Program received signal SIGILL, Illegal instruction.
0x0062d24c in juce::enumMonitorsProc ()
(gdb)

The “C:\Program Files (x86)\CabbageStudio32” path gets fetched from environment variables, it’s probably some residue from an earlier install. Let me just try to remove it and try to launch…

…(time passes)…

nope, back to windows, and same response from gdb

but SIGILL seems worth investigating, no?

I have no experience with the juce library though…

#26

just to be clear:

“C:\Program Files (x86)\CabbageStudio32” is not read from environment variables. I removed the “OPCODE6DIR” variable, the variable entry for “CABBAGE_OPCODE_PATH” and gdb still shows the studio path.

#27

That is interesting. And perhaps we are getting to something here. There should be no mention of CabbageStudio in any system paths. Nor do you need OPCODE6DIR64, unless it is put there by the regular Csound installer, in which case you can leave it there.

What exactly do you mean when you say

Where do you see this? I don’t see anything in the gdb output regarding this particular path?

#28

Sorry I messed things up a bit here.

This is what happened:

I removed the OPCODE6DIR variable, which entry contained “C:\Program Files (x86)\CabbageStudio32”.

I also removed the “C:\Program Files (x86)\CabbageStudio32” entry from the CABBAGE_OPCODE_PATH variable.

this is the current gdb output from the debug build:

(gdb) run
Starting program: C:\Program Files (x86)\Cabbage32\CrabCakes.exe
[New Thread 5436.0x17dc]
[New Thread 5436.0x17d0]
[New Thread 5436.0x1ad8]
[New Thread 5436.0x1714]
[New Thread 5436.0x1aa4]
[New Thread 5436.0x181c]
[New Thread 5436.0x1598]
[New Thread 5436.0x14a0]
[New Thread 5436.0x1534]
[New Thread 5436.0x1844]
[New Thread 5436.0x1aac]
[New Thread 5436.0x18dc]
[New Thread 5436.0x18cc]
[New Thread 5436.0x1af4]
[New Thread 5436.0x1b40]
warning:

Cabbage opcode plugins are located at:C:\Program Files (x86)\Cabbage32

warning: Current opcodeDir is:

warning: compiled Ok

warning: about to cleanup Csound

warning: Csound cleaned up

[Inferior 1 (process 5436) exited normally]
(gdb) quit

------ and here’s the current gdb output from the release build:

(gdb) run
Starting program: C:\Program Files (x86)\Cabbage32\CabbageStudio.exe
[New Thread 6804.0x4a0]
[New Thread 6804.0x13e0]
[New Thread 6804.0x12a4]
[New Thread 6804.0x1d40]

Program received signal SIGILL, Illegal instruction.
0x0062d24c in juce::enumMonitorsProc ()
(gdb) quit

so, after removing the environment variables, the path “C:\Program Files (x86)\CabbageStudio32” is not mentioned anywhere anymore.

#29

Thanks, I’m still baffled as to why C:\Program Files (x86)\CabbageStudio32 was adding to the CABBAGE_OPCODE_DIR. Did the installer do this I wonder? Would you mind running the installer again and then checking CABBAGE_OPCODE_PATH, just don’t forget to move the working version of Cabbage Studio or it will overwrite it. Sorry about all this. Debugging the problem remotely isn’t very convenient!

#30

been away from computer for a few days,

but now I’ve tried installing (0.5.17) again, and the only environment variable it adds is “CABBAGE_OPCODE_PATH” with a value of “C:\Program Files (x86)\Cabbage32”.

I think the path “C:\Program Files (x86)\CabbageStudio32” was added by an older version, perhaps 0.5.13, which I had before.

#31

Thanks for the confirmation. That’s good to know.

#35

I’m closing this topics as it relates to the older version of Cabbage which is no longer under development.

#36