release-mode

Not sure if that's an issue with Swift, XCode or Alamofire but I recognized strange behavior on different places within my mixed Swift/Objc app . It only happens in parts which are written in Swift and use closures/networking. Here's an example code where it happens: Alamofire.request(.DELETE, "http://someUrl.com/user", parameters: nil) .response { (request, response, data, error) in // some cleanup code and an alert } When I run my app in Debug mode on my iPhone then it all just works , the cleanup code and the alert get presented like they should when I do the "delete account" action which

I am trying to port a small app of mine from Win XP and VS 2005 to Win 7 and VS 2010. The app compiles and runs smoothly in Debug mode, however in Release mode I get the following error: pcrecpp.lib(pcrecpp.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in LoginDlg.obj Where should I start checking? Your app is being compiled in release mode, but you're linking against the debug version of PCRE, which had /MTd (or similar) set, thus causing the mismatch in iterator debugging level in the CRT. Recompile PCRE in release mode to match your

I am new to C# and VS 2010, and am following an online guide to creating a C# Windows Service in Visual Studio 2010. When I try and build the application however, I don't get any files created under the /bin/release folder. I do get files under the /bin/Debug folder. I have tried all the build configurations e.g Active, DEBUG, Release, All but nothing changes. I have tried closing the solution down and restarting etc. I have also experienced this same problem on a number of other projects which have been C# console apps. The /bin/release folder exists (as I had to create it by hand) and I have

I've been trying to use XMVECTOR as a class member for a bounding box, since I do a lot of calculations, but I use the XMFLOAT3 only once per frame, so the bounding box has a method that gives me it's center in a XMFLOAT3, otherwise it stays in a XMVECTOR;The class is delcared with __declspec(align(16)) and works in debug mode.However in Release mode it crashes the instant I set it to something: Box& Box::operator=(const Box& box) { _center = box._center; _extents = box._extents; return *this; } Whenever I do: Box A; Box B; A = B; It crashes, giving me 0xC0000005: Access violation reading

I know PDBs are generated for managed projects in .NET by giving the compiler the /debug argument. Is there a way to specify this in the VS (2005) GUI? The only way I could get it to generate PDBs in release mode so far is to manually modify the .csproj file and to add : <DebugSymbols>true</DebugSymbols> <DebugType>full</DebugType> under the 'release' settings: <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "> Another thing: I learned from MSDN here that the possible values for the DebugType tag are: full pdbonly none How do these values affect the compiler's

I've written a method for pushing real-time location data to Firebase: private void writeNewMarker(int sessionType, String myUuid, String datetime, Location location) { locationToDB = new LocationFromAndroid(); JSONObject jsonObjectCoords = new Coords(location.getLatitude() + "", location.getLongitude() + "", location.getAltitude() + ""); locationToDB.setFinish("false"); locationToDB.setLost("false"); locationToDB.setCoords(jsonObjectCoords); locationToDB.setDistanceToGo("0"); locationToDB.setHeading(location.getBearing() + ""); locationToDB.setNauwkeurigheid(location.getAccuracy() + "");

I have an app I'm writing that crashes when I call addSubview on a UIScrollView with "EXC_BAD_ACCESS". It only does this on iPhone 3G in release mode and only on the device. I works fine in all these other configurations: iPhone 3G - Debug mode iPhone 3GS - Debug AND Release Mode iPhone 4 - Debug AND Release Mode Simulator - all. Furthermore, there is no rational reason why this should be happening. My object is not released by any of my code. I had the exact same problem recently, however I am not entirely sure the cause is the same. What I can tell you though is what resolved the issue for