odds are it's not the fprintf that's causing the error.
can you reduce this to some example code that causes the error?
Does an fprintf at the beginning of main() cause the error? how about the very end?
fprintf causes seg fault??
yes
putting fprintf at the start of main still causes the problem
rather than seg faulting tho, i get 'this program has cause a problem and needs to close' message from microsoft
mainly because at the begginging of main SDL hasnt been started up, so windows catches it instead
still a seg fault tho
putting fprintf at the start of main still causes the problem
rather than seg faulting tho, i get 'this program has cause a problem and needs to close' message from microsoft
mainly because at the begginging of main SDL hasnt been started up, so windows catches it instead
still a seg fault tho
OK
my SDL expert friend found it
i dont completly understand it
but it seems that i needed to setup my project to do something about 'multithreaded dll' since SDL is multithreaded
thanks for everyone offering suggestions
pointy clicky gui goodness
i really hate not knowing whats really going on when i mess with these msvc menus and buttons......
my SDL expert friend found it
i dont completly understand it
but it seems that i needed to setup my project to do something about 'multithreaded dll' since SDL is multithreaded
thanks for everyone offering suggestions
pointy clicky gui goodness
i really hate not knowing whats really going on when i mess with these msvc menus and buttons......
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement