[bug] Conflicts with DLLS written by go

[Hi-Mr-Wind]

Describe the bug

When I was writing tauri2.0-rc, I used rust to call the dll compiled by go, but I found that after the dll's calling method was executed, the UI would exit without printing the wrong stack content, just like calling exit. But neither my dll nor rust code calls a similar method, I wonder why it causes the exit

Reproduction

No response

Expected behavior

After testing, the dll written by C++ is called, and no exit phenomenon is found after the execution of the method. However, the completion of the execution of the dll generated by go and other languages will cause the end of the UI process

Full tauri info output

pnpm tauri dev

Stack trace

He exits after printing without stack

Additional context

No response

[FabianLars]

I'm afraid this is impossible for us to triage like this. Please post the output of pnpm tauri info as required by the issue template.
Also, we'll need some kind of minimal reproduction example here...

Since afaik we don't have any Go experts/users on the team i'll mark this issue as help wanted too.

[vednig]

Please provide the response code returned after running dll