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

va_copy change causes va_arg functions to break #184

Closed
michaelrsweet opened this issue Sep 7, 2016 · 5 comments
Closed

va_copy change causes va_arg functions to break #184

michaelrsweet opened this issue Sep 7, 2016 · 5 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@michaelrsweet
Copy link
Owner

Version: 2.10
Original reporter: Steven Warner

I found that va_copy had been changed to copy "&dst from src" instead of original "&dst from &src" this caused functions like mxmlElementSetAttrf to break.

Reinstated the "&dst from &src" which stopped the exception, but still getting a load of heap errors where most if not all of xml output is being kept in memory and not removed from heap.

@michaelrsweet
Copy link
Owner Author

Original reporter: Michael Sweet

What OS and compiler are you using?

@michaelrsweet
Copy link
Owner Author

Original reporter: Steven Warner

Building for Windows 32bit and 64bit
Using Visual Studio 2010

NOTE: heap errors had increased with 2.10 but the mxmlDelete (bug 551) changes reduced that back to what we previously had. (we've been living with a small memory leak from mxml for a while now - we will have to find the source of it soon though it's getting annoying)

@michaelrsweet
Copy link
Owner Author

Original reporter: Steven Warner

Correction:

Found long running leak in our code was result of external client retaining output from mxml.

'va_copy change causes va_arg functions to break' issue still present though

@michaelrsweet michaelrsweet added the bug Something isn't working label Mar 3, 2017
@michaelrsweet michaelrsweet added this to the Stable milestone Mar 3, 2017
@michaelrsweet
Copy link
Owner Author

Will re-test with current Visual Studio, but this looks like a VC++ bug; if VS 2017 still has this issue I'll just add an #ifdef WIN32 and note that this is a Windows bug...

@michaelrsweet
Copy link
Owner Author

OK, came up with a solution that eliminates the va_copy on Windows entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant