Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

formatInt from scriptstdstring add-on crashes with Jit #17

Open
TheExDeus opened this issue Feb 21, 2015 · 5 comments
Open

formatInt from scriptstdstring add-on crashes with Jit #17

TheExDeus opened this issue Feb 21, 2015 · 5 comments

Comments

@TheExDeus
Copy link

When I use AngelScript-JIT my application crashes (with corrupted stack so no backtrace) when I use formatInt in scripts. When I disable JIT it works fine. Strings themselves also works fine, but only formatFloat and formatInt crashes. parseFloat and parseInt doesn't crash.

Maybe others can replicate this?

AS version is AngelScript 2.29.2.

@ThyReaper
Copy link
Member

I cannot replicate the issue. Could you provide a script that reproduces the error for you? Are you building 32 or 64 bit, and for Windows or Linux?

@TheExDeus
Copy link
Author

I'm building 32bit on windows. I'll try reducing the code size. The issue might be with something else, as AS is a part of a much larger system.

@TheExDeus
Copy link
Author

I can replicate the problem with Tutorial example that comes with AngelScript. Just add JIT to it and call a script having formatFloat or formatInt in it.
Here is the script: http://pastebin.com/PcWkFMjm
Here is the modified example: http://pastebin.com/eQzsb9cu

Even in this simple example the stack trace cannot be recovered, so I cannot really tell you what the problem is.
I compile with gcc 4.9.2.
Full config: http://pastebin.com/qgsshjg5

@ThyReaper
Copy link
Member

Unfortunately, your reproduction case does not reproduce the issue for us.

@xKamuna
Copy link

xKamuna commented May 11, 2017

This also happens for me, too, so it definitely happens on multiple computers. Even changing the name or definition to use to_string doesn't work. The workaround is to use the Generic versions of these functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants