Debugger Stops if Calling TensorSplitsCollection about llamasharp

[martindevans]

When the TensorSplitsCollection is created it runs this code:

internal readonly float[] Splits = new float[NativeApi.llama_max_devices()];

If you just try to execute that, does it crash in the same way?

[hswlab]

I'm only using the nuget package right now on my notebook and can't edit the llamasharp code. But I tried calling NativeApi.llama_max_devices() in my code directly and the same thing happens. The debugger aborts. It seems, that llama_max_devices can't be callen on my notebook .

[martindevans]

The NativeApi call just directly calls llama.cpp and there's no other C# code involved, so I think you'll have to report this one to llama.cpp.

[martindevans]

I went to look at llama.cpp and the contents of llama_max_devices are:

int llama_max_devices(void) {
    return LLAMA_MAX_DEVICES;
}

So there's probably something else going wrong here!

[hswlab]

I currently have looked at the ModelParams method on PC and notebook in the debugger. Somehow this method looks different. On the PC the constructor looks like this.

But on the notebook the constructor looks like this

I'm actually using the same GIT status on both pcs. If the constructor on the notebook and PC were swapped, it probably wouldn't crash when calling llama_max_devices, because my PC has no problems with this method. But I don't understand why the constructor looks different at all. Maybe I'll see a bit clearer tomorrow^^.

EDIT:
Oh man. I'm really sorry. I figured it out. I tested on both PCs with the same Settings (avx2). But my notebook only supports avx. This was my mistake.