I have an Xcode project that has been upgraded to Xcode 3.2, and whilst it builds fine (and produces an executable that runs fine), when I try to debug it the debugger doesn't start.
When I look in the debugging window, it says that the build was fine. When I look in the console, I get a 'Session started ', but the application never begins.
I've had a wander through the build settings, and can't see anything that appears to be turned off when it should be turned on. I thought it may be a new setting that I need to turn on, but I can't see anything of interest that may help.
Any advice would be grateful accepted!
Cheers and thanks.
Have you tried a full Clean of the project?
I was having the same problem and just discovered that my app launches on the iPhone correctly when I've started Xcode from the finder, but not when I've launched Xcode from my shell. For example, I start Xcode by typing "open project.xcodeproj" into my bash terminal, and device debugging is broken, but if I start Xcode via spotlight or by double-clicking on my project, or from the Applications folder, device debugging works fine. I'm not certain, but it appears to be a problem with my shell environment variables.
Thanks to Rob for the advice. I tried rebuilding everything a couple of times and still to no avail.
However, after turning on my machine this morning, trying the project out it now debugs quite happily. I'm guessing that after installing Xcode I should have rebooted the machine (it didn't require one according to the installer).
Thanks all.
Related
I cannot run my Code from the play button anymore, it just shows "nothing here" (see image below). If I try it using the button in the top right corner, it works just fine, but it's really annoying to switch the files which I want to run every single time.
I really did not change any settings, it just happened out of nowhere. I already tried finding solutions on multiple forums, but couldn't find any answers either. My lucky guess would be that it has something to do with the ide.properties file?
Has anyone experienced something like this before? I'm using IntelliJ IDEA Ultimate 2019.3 on MacOS Catalina.
Same problem with a collegue using MacOS Catalina. Downgraded from 2019.3.1 to 2019.3 using the toolbox fixed the problem. After upgrading again to 2019.3.1 (and invalidating caches) we still didn't have the problem anymore.
Not a real fix, but maybe it helps.
I'm having some trouble working with xCode. It just keeps hanging and using 100% CPU right after a couple lines of code. I'm working on a new project and it barely has two files and it has become completely imposible to work with.
I tried reinstalling xCode and starting my project from scratch but it won't work.
I noticed three things that may help someone find out what it's going on.
It's slow even when typing, the characters appear delayed on the screen.
It keeps saying indexing on the task bar on top. If I clean the project it will disappear but come back whenever I start working again.
It overheats as soon as I open xCode
And here's some other facts that might help
I'm running xCode 6.1.1 (build 6A2008a)
My Mac is a mid 2012 MacBook pro 8GB Ram
I did a fresh install of Yosemite a month after it was released, so it's pretty clean.
I'm using the latest build of Xampp for my SQL server
I'm using nodejs as a backend so I'm running an http with nodemon
Hope any of you has a solution to this.
Thanks and merry christmas to all of you.
EDIT
I found out that it will build just fine if I remove my conditional cast to NSInteger, NSString, Float, etc. I have like 8 of them one after the other, and just replacing as? for as did the trick. I'm curious as for why this is happening anyway though.
Similar problems on 6.1.1 (but also source kit crashes) were improved (but not completely resolved) for me by deleting derived data.
I'm working on an iPad app and I need to try a few things, for which I usually have a small sample app that I use. While my primary app project opens just fine, the sample app doesn't. Xcode (Version 5.0) just sits there, the wait cursor spinning. The other odd thing is that when trying to make a new project, I get the same behavior.
What's going on here? Various other threads on Stack and other forums suggest removing various files, in ~/Local/... and in the .xcodeproject directory. However this doesn't seem to help. Any ideas as to what's going on?
I restarted my macbook and XCode behaves now. There goes my 200 day uptime...
i have an app that when i run on xcode connects with the database and retrieves the required values PERFECTLY.
But when i run the actual application in the Debug folder, it not only does not access the database , it also does not go into any of the functions in my code.
Why can an application show this type of behaviour? It never happened before to me. I have an old copy of the code which works fine. I have clear the targets and built it like 10 times but still runs perfectly on xcode but the app individually isnt quite working..
Thanks in advance for any help .
I am out of ideas and i have no direction to go to as from a programming perspective the code does its work.
memory management issues... be sure to remember [database release] instead of autorelease which works fine on the xcode but crashes the app in mac os
Visual Basic 6 is crashing after a new build of my program. Whenever I Start (F5 or Ctrl-F5) my program after making changes to the code, VB6 crashes with the following message:
An unhandled win32 exception occured in VB6.EXE [XXXX].
I can't make any pattern out of XXXX. It's been 5168, 5012, 1488, etc; it changes every crash.
The JIT debugger then offers to let me debug VB6 in VS2010 (which shows nothing but a bunch of disassembly.) If I say no, VB6 shuts down. I can then open and Start my program immediately, and it runs just fine; my changes from before the crash were saved. Alternatively, I can make changes, save them, exit VB6, restart VB6, then run them without a problem. But it seems like as soon as I make any changes, a "crash" flag is set, and if I try and build it before restarting VB6, it simply dies.
I'm only having this problem with specific projects. Most projects work completely normally. It's just this one, and it's branch, that both act in the same manner.
Does anyone have any clue what's going on? Obviously, saving works. And building works. And running works. They just don't seem to work together.
I reinstalled VB6 to no avail.
I ended up on this page after installing VS2010, and just one of many VB6 project wouldn't compile.
Simply go to Project Properties / Compile tab, and uncheck "Create Symbolic Debug Info".
Hope it works for you.
Try to open vb6 project with compability mode as XP. We had some issues related to "make exe" command. Then I started to run VB6.exe with XP compability mode.
Since you're asking for any clues, possible clues may include:
The surprises VB6 experiences when run on Vista/7. Try running elevated/remove elevation.
Same, but applied to a third party ActiveX control you're using.
Not having the Service Pack 6 installed. Install it.
Subclassing issues. Make sure your subclassing, if any, is actually correct.
Whatever problems you'll never figure out. Try reinstalling.
Reinstall VB6, delete the workspace files and then create a new project adding in all your current code files. Then go out and get a job where they use a modern SDK :)