-
Notifications
You must be signed in to change notification settings - Fork 1
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
Character encoding issue ? #2
Comments
when getline() is inlined by the compiler, it resorts to using and linking against the __getdelim function from the standard library. However only the getdelim function was covered by pdwfs, not the __getdelim Besides no tests were actually covering getline and getdelim...bad, very bad.
Hi Mat, I think I managed to reproduce your issue. Actually this is not an encoding issue, but it's definitely a bug. The reason why I have pushed the branch I hope that you actually used |
btw, you can easily check what calls are intercepted by pdwfs by running it with the |
I am using
and it looks like it is not intercepted neither according to the run with the trace activated:
Anyway, I was just trying out how this works with hello world examples. But I agree, in a real code you might want to read the full buffer with a I'll have try with your branch, but first I need to compile pdwfs. Until now I made the minimum effort using the available binaries 😊 |
I've just tested with fread and parsing it in memory, it works ! |
yay! |
ok my bad, interception of but failing an hello world example looks pretty bad...so we'll make it work! |
ok, I managed to compile and run my hello world with the
Tell me when I can I have a new try. |
The small hello world example in C I am using |
Describe the bug
I am new to pdwfs. It looks really nice but the result of the simple example I tried to build is different with and without pdwfs.
How to reproduce
Expected behaviour
So I expect to have a single "Hello444" in resC which is the case without using pdwfs. When using it I get the following:
Am I doing something wrong ? Anything related with character encoding ?
Thanks for your help
Mat
The text was updated successfully, but these errors were encountered: