XCode debugging problems

For some reason, when I try to debug or run my application within XCode, my Application menu does not appear, and keys pressed go to the runlog window, not my application controls.
Any Idea what's going on, or how I should start troubleshooting this problem?

It sounds like your Info.plist file is messed up. I used to get that problem when I was first using Xcode. The best way to fix it is to create a new Cocoa application with nothing in it. Compile and run it to make sure it works correctly. Then, inspect the Project and Target settings. I don't remember precisely where the problem was. Usually, it was something related to a mismatch involving the name of the application. I had renamed my app something different than MyApp and didn't use the new name everywhere.
Anyway, inspect those settings. Your GUI has become disconnected from your application. Sorry I can't provide more help. It has been several years since I had this problem. I have since learned to pick a good application name when I create the project and stick with it.

Similar Messages

JApplet debugging problem

Hi there all:
I'm having a problem with debugging a JApplet. I created a new workspace, project and applet and didn't make any changes to anything. When I try to debug the applet, I get these messages:
System Error: java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThreadGroup )
System Error: java.lang.Object java.lang.Class.newInstance0()
System Error: java.lang.Object java.lang.Class.newInstance()
System Error: java.applet.Applet sun.applet.AppletPanel.createApplet(sun.applet.AppletClassLoader)
System Error: void sun.applet.AppletPanel.runLoader()
System Error: void sun.applet.AppletPa
System Error: nel.run()
System Error: void java.lang.Thread.run()
If I change the object from a JApplet class to an Applet class, I can debug just fine.
Anyone know what's going on here?
Thanks
Jeff

Me again. Was doing some searching on the net about this one since I've gotten no response.
Found this at Inprise (Borland) about a debugging problem with JBuilder3 (I assume that the base of jdev is still JBuilder).
http://community.borland.com/article/0,1410,19739,00.html
To quote from their document--------
Question:
I can't seem to debug Applets with JBuilder3 Standard. If I attempt to debug my Applet
I recieve the following error:
java.security.AccessControlException: access denied (java.lang.RuntimePermission
modifyThreadGroup )
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:195)
at java.security.AccessController.checkPermission(AccessController.java:403)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
Why?
Answer:
In a nutshell this is an installation problem with JBuilder3 Standard edition.
The install for JBuilder3 Standard did not provide the file 'DebugApplet.policy'.
To resolve this problem download the file from the following URL:
http://www.borland.com/devsupport/jbuilder/downloads/DebugApplet.policy
After you have downloaded the file, copy the file to your JBuilder3\bin directory.
This will fix the problem.
You can also cut and paste the following:
(NOTE: create the file DebugApplet.policy in your JBuilder3\bin directory)
//DebugApplet.policy
// These policy permissions are needed for the AppletViewer used by sun.tools.debug.
grant {
permission java.lang.RuntimePermission "accessClassInPackage.*";
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.net.SocketPermission "*", "accept, connect, listen, resolve";
permission java.util.PropertyPermission "appletviewer.version", "read";
permission java.io.FilePermission "<>", "read";
permission java.security.AllPermission;
Could this be a problem in JDev3 too?
Jeff
null

XCode 4 Problems

Is anyone else experiencing consistent crashes in XCode 4? I can duplicate the problem by setting a breakpoint in a multi-threaded app, waiting 40 seconds after the breakpoint is hit, and clicking another tab. The CPU utilization goes to 100%, and I have to force quit xcode. This makes it impossible to debug my multi-threaded apps.

We have been experiencing many problems using Xcode 4 with iOS SDK 4.3. Often the problems are intermittent, but much time is wasted working around them (too often requiring quitting Xcode and restarting). e.g.:
Crash on launch of Xcode 4 whenever the "x project is locked for editing... Do you want to unlock it?" Select "Do not show this message again", then click [Don't Unlock]. Crash.
Debugging with GDB sometimes results in the project details window showing when a breakpoint is hit or attempting to step thru the code, requiring hunting thru the navigator to get back to the related source file where the PC is holding at.
Intermittently features like command clicking on a class or function name do nothing, instead of going to the related source file.
I'm about ready to revert to Xcode 3.

Sun Studio Debugging problem

Hello
I need help configuring the Sun studio debugger to work in fedora 8. The project is loaded from a make file, compiles fine, and runs fine. However, I can not place break points, and when I start the visual debugger, it gives a message box titled progress, and hangs on saying: starting debugger: /lib/libc.so.6
Running from the command line gives me:
$dbx <my program>
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc
Reading <my program>
Reading ld-linux.so.2
Reading libm.so.6
Reading libmpich.so.1.1
Reading libpthread.so.0
Reading librt.so.1
Reading libc.so.6
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
I have another problem in debugging an mpi problem in another installation of Sun Studio on Solaris 10 on a Sun machine. The visual debugger is working fine there, however, I need to debug with mpirun
to decide the number of processors, because by default it loads the application on one processor. Iwill need to do this as well later on the linux machine I am using now, which doesn't even start the debugger on a sequential code so far.
I appreciate your help a lot.
Thank you very much in advance.
Manal

mhelal wrote:
Hi
Thank you for your reply. you said 2 problems,Yes, basically I meant these two:
1. dbx: warning: unknown location expression code (0xe0)
2. dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
First one should be fixed in dbx itself, but the second looks like an incompatibility between Fedora's libc and dbx; unless distros in "supported" list upgrade to the same version of libc, dbx can't be changed to match it.
In other words, I'm sorry to say that you will probably not succeed in using dbx on Fedora 8 for the time being.

XCode connection problem with XCode

Hi!
I need some advice with my developer environment. When i got my dev-licence everything worked fine. But after som days my iPhone started to beap and XCode failed to connect to the iPhone. Some times it had a short connection for i minute or so.
I have tested different usb cables. I have tested to restart my Mac, iPhone in different combinations.
After upgrading iOS SDK my problems was gone for some day.
I don't need to have XCode running to make the iPhone beap.
My phone have some sequirity patches from the Company i work for.
My setup: XCode 4.5 Mac Mini OSX 10.7.4
Thankfull for all help!
/Mikael

My phone have some sequirity patches from the Company i work for.
Good trick! Care to elaborate on how your company applies security patches to an iPhone?

Debug problem using JDK 1.2.2

Hello,
I set up remote debugging in J-Dev 3.1.1.2 and was using it successfully for several days.
I then did some local debugging on a servlet that was compiled using 1.1.8 JDK. Now none of my servlets that are compiled under 1.2.2 can be debugged either locally or remotely. I get a message telling me that the class cannot be debugged.
Can anyone offer suggestions on what could be wrong?
Thanks

I had this problem earlier today. I deleted the old workspace, created a new one, added my projects in again, recompiled and things were fine. Every now and then my workspaces seem to corrupt and I have to do this, although I don't always get the "can't debug class message"
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Bill:
Hello,
I set up remote debugging in J-Dev 3.1.1.2 and was using it successfully for several days.
I then did some local debugging on a servlet that was compiled using 1.1.8 JDK. Now none of my servlets that are compiled under 1.2.2 can be debugged either locally or remotely. I get a message telling me that the class cannot be debugged.
Can anyone offer suggestions on what could be wrong?
Thanks <HR></BLOCKQUOTE>
null

Debug problem in JDeveloper 3.0

Has anybody come across a problem when debugging an application that causes JDeveloper to go into an infinite loop (until my machine runs out of memory) when a breakpoint is hit.
This only seems to happen on certain files
I've removed JDeveloper 2.0. I've reinstalled JDeveloper 3.0. I've recreated my workspace and project from scratch but I still get the problem.
My project has ~1200 files.
I've also noticed that sometimes the breakpoint is hit and the application being debugged will be paused but JDeveloper does not gain control (i.e. the 'step', 'step into' etc. buttons are still disabled). This is possibly related to the above problem.

Has anybody come across a problem when >debugging an application that causes >JDeveloper to go into an infinite loop >>(until my machine runs out of memory) when a >breakpoint is hit.This is not a known issue but if anyone has a reproducable test case then we'll be happy to follow it up.
Thanks,
Arun

Java debugging - problems with standard input

Hi
I hope somebody can help me with this problem.
I'm developing a Java app that reads from the standard input. I use System.in.read() to do that. When I debug it, I use the Standard I/O window instead of the Run Log window to pass in values, but nothing happens (i.e. the line following the read() is never reached). I also tried to run the app and then attach the debugger to use the Run Log window as standard input, with the same result. If I add a breakpoint before the call to read(), the debugger pauses the execution, so I suppose the breakpoints are OK.
In the executable Info window, Debugging tab, I use the pseudo terminal with the Java debugger.
So my question is: how can I enter values from the standard input in debugging mode?

I believe that you are seeing these problems because we have found the
current versions of RMI found in the JDK to be inherently unscalable -- we
do not listen for them. As you noticed, we recommend that you use our
packages for now, and then do the simple change that you found if you decide
that you do not like WLS. (If you do decide that you do not like us, please
definitely let us know why you chose the way you did!)
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Tim Dawson" <[email protected]> wrote in message
news:397b8cc2$[email protected]..
We're developing a J2EE application on NT using WLS 5.1, SP3, but we don't
want to be tied to any particular J2EE server, so we're making sure that
none of our code is weblogic specific.
In keeping with this philosophy, I created an RMI service that used the
standard java.rmi.* imports instead of weblogic.rmi.* and used thestandard
RMIC compiler rather than the weblogic.rmic compiler.
Unfortunately, I couldn't get the system to work. I kept getting
"java.rmi.MarshalException: Error marshaling transport header; nested
exception is: java.io.EOFException" whenever I'd call Naming.lookup().
Of course, when I did the search & replace with java.rmi.* with
weblogic.rmi.*, and switched from the standard rmic to weblogic.rmic,
everything started working just fine. This is the ONLY change I made!
Has anyone else run into similar problems?
Tim Dawson
Sr. Software Architect
is.com

Xcode snapshots problems

It seems in Xcode I'm at a point where the snapshots will no longer work for me. When I make a new snapshot, it always shows every file in the project in the "Files Added" category and there will not ever be files in the "Files Changed" category. Older snapshots a few files in the "Files Changed" category but no new ones do.
Does anyone know what to do here?
I've tried removing directories in ArchiveDirectories, editing the Snapshots plist file, removing the snapshots image (~Library/Application Support/Developer/Shared/SnapshotRepository.sparseimage), among other things.

That was easy. The DU output appears in the console log. Here it is:
12/23/08 12:30:27 AM Disk Utility[9894] Repairing permissions for “Hina”
12/23/08 12:30:27 AM Disk Utility[9894] Reading permissions database.
12/23/08 12:30:27 AM Disk Utility[9894] Reading the permissions database can take several minutes.
12/23/08 12:36:13 AM Disk Utility[9894] Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
12/23/08 12:37:03 AM Disk Utility[9894] Permissions differ on "System/Library/LaunchDaemons/com.apple.usbmuxd.plist", should be -rw-r--r-- , they are -rwxr-xr-x .
12/23/08 12:37:04 AM Disk Utility[9894] Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
12/23/08 12:37:04 AM Disk Utility[9894] Warning: SUID file "usr/bin/setregion" has been modified and will not be repaired.
12/23/08 12:37:12 AM Disk Utility[9894] Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
12/23/08 12:37:12 AM Disk Utility[9894] Warning: SUID file "System/Library/Printers/IOMs/LPRIOM.plugin/Contents/MacOS/LPRIOMHelper" has been modified and will not be repaired.
12/23/08 12:37:12 AM Disk Utility[9894] Group differs on "private/etc/cups", should be 0, group is 26.
12/23/08 12:37:12 AM Disk Utility[9894] Permissions differ on "private/var/spool/cups/cache/rss", should be drwxr-xr-x , they are drwxrwxr-x .
12/23/08 12:37:22 AM Disk Utility[9894]
12/23/08 12:37:22 AM Disk Utility[9894] Permissions repair complete
Doesn't look like it should have helped Xcode at all. This is what I remember with certainty:
1. I made a snapshot days after installing the 10.5.6 update (directly from Software Update.)
2. I got the "(no changes)" message when comparing that snapshot with the previous one.
3. I quit Xcode, relaunched, and the problem had disappeared. All diffs showed up.
4. Days later, I made another snapshot and "(no changes)" appeared when comparing any snapshots. This time, quitting and relaunching Xcode didn't help at all. The 12-15 and 12-20 folders contained identical files despite my having made many changes.
5. I tried restoring the SnapshotRepository.sparseimage via Time Machine, mounting the image and looking for missing files, etc. Couldn't find any signs of corruption. Never touched any preferences files though. Nothing helped. This is when I made my original post.
6. Ran DU "repair permissions" just for grins, and suddenly "it just worked." The latest snapshot that I had made (the one that that seemed to trigger the problem) and all others now show the expected diffs, some of which are quite extensive changes.
7. Subsequent snapshots also show the correct diffs. So I thought DU had fixed the problem. Maybe not.
Now, here are some things that I did that directly affected the repository image. I just can't remember exactly when I did them:
- At some point I deleted a snapshot using the Xcode interface by choosing a snapshot and clicking Delete. I can't remember exactly, but I'm pretty sure I deleted the last one at the time (dated 12-20, which, when I mounted the image, contained files that were physically identical to the 12-15 snapshot's.) This would have probably happened at some point between steps 5 and 6 above, but I'm not sure.
- I'm pretty sure I made at least one other snapshot on the 20th, got the same "no changes" message, and just gave up fiddling around. Waited a few days, made a few more changes, then posted here.
Sorry for burning up all that bandwidth. It really doesn't look like permissions could have caused the original problem (the 12-15 and 12-20 snapshots containing identical files despite my changes in Xcode.) But somehow things are fine now.

Debugging problem, in inbound function module.

Hi Experts,
              R/3 system is receiving data through an IDOC called WPUUMS[sales data]. It has been seen that when this data is posted in R/3 through XI the data gets reflected in WE02 / WE05, and is similar to when a manual entry is done the transaction WPUK. But the difference is , when manual idoc generation is done, it is updating correct data in database, but when same data is posted from XI, it is updating data base with in correct data!
   what I cant get to understand is in both the cases, IDOC is posted, and same data is there in the DATA records, but database is getting upated with diff data.
    Also , when I am putting a break point on the inbound function module IDOC_INPUT_POS_SALES_ACCOUNT, it is not hitting the break-point but idoc gets generated successfully with status records like
53 Application Document posted
62 Idoc Passed to application
64 Idoc ready to be transferred to application
50 Idoc added.
Also , i want to know, wether these messeges come step by step or randomly, because, why is the messege 62, before messege 64.
Lastly when I am taking the same IDOC and trying the same in WE19, then it hits the break-point function module IDOC_INPUT_POS_SALES_ACCOUNT successfully.
Experts, comments pls.!
Regards,
Arnab.

Hi,
You are supposed to read the ststus messages from bottom to top. So the actual sequence is:
50 Idoc added.
64 Idoc ready to be transferred to application
62 Idoc Passed to application
53 Application Document posted
Which is correct.
And it is correct that the system bypasses any breakpoint in the background mode. So when the IDoc is coming from XI the posting FM IDOC_INPUT_POS_SALES_ACCOUNT is called in background and so the breakpoint is not called.
Only way to debug the problem is via transaction WE19 in Debug mode.
Regards,
Prakash Pandey

Xcode debugging help

I'm new to xcode, so I don't really know how to use much of it, so here's my problem: I started a fairly simple project with version 2.0 (came with tiger) and I got about half way through and it was working great. Then I realized that it wasn't universal, so I downloaded xcode 2.4.1. When I tried to build it as universal I got a bunch of errors, and I have no idea what it means or how to fix it! I'm coding in applescript, and when I run the app via the debugger, it all seems to work just fine, but it won't build because of some errors. Can anyone give me any insight as to what this all means? I couldn't seem to copy and paste, so I took screenshots:
pic 1
pic 2
Thanks!
p.s. - Can you include images in posts?!

It appears that you may not be linking against the Universal libraries. But here are some things to check.
I believe your "target" has to be a "native" target in order to build universal binaries. Older projects that are brought forward may not be "native"... I'm not sure exactly when this changed so I'm not sure if your 2.0 Project would've been "native" or not. Select the top level "project" icon in the "Groups & Files" pane (the one with the little Xcode icon). Then select the "Project" menu on the menu bar... if "Upgrade all Targets in Project to Native" is dimmed out then you're already native and you don't need to do anything. If it's not dimmed then select it to upgrade your targets to "native" format.
With the top level project item still selected click on the "Info" button in Xcode's toolbar (or select "File -> Get Info" from the menu bar). In the Info window click the "General" pane. Check the pop-up setting for "Cross-Develop Using Target SDK:"... it should be set to "Mac OS X 10.4 (Universal)". Change it if it's not.
While still in the Info window, click the "Build" tab. The first setting in the list should be "Architectures" and it's value should be "ppc i386". If it's not then select that line and click the "Edit" button to turn on the checkboxes for both PPC and Intel. The second item in the list should be "SDK Path" and should be set to "/Developer/SDKs/MacOSX10.4u.sdk". If it's not then select that line and click "Edit" to enter the path to the sdk (without the quotes).
Check those items and post back if it doesn't fix your problem.
Steve

Debugging problems on iPad

I have two applications, and 4.7 installed in two different PCs (64 bits one and 32 bits the other one).
In one PC (32 bits) both apps can be tested with no problem at all. In the other one (64 bits) I debugged one of them once, but now I can't debug any of them.
Problem description: device is there and connected, debug begins, says it's installing and seems to finish it well. It waits for me to initiate the app, but the app is not there. No app for debugging in the iPad.

Hi,
A similar issue has been logged and is being tracked. Please refer to below bug for more description.
http://bugs.adobe.com/jira/browse/FB-33478
Workaround: Even though ipa is not installed on the device, ipa will be generated in the specified output folder(bin-debug).Using iTunes install the ipa on the device and launch the app to make a debugger session.
Let me know if you require more information.
Thanks,
Sanjay

Debug problem

I installed the sneak preview Enterprise portal on my machine. Yesterday i was able to debug my portal application. But today i wasn't. This problem was after the moment I deleted the old portal application.
Can someone tell my how i can fix this problem
Message was edited by: Edward Kust

It could be that your IP address has changed?! In this case, the Developer Studio/Eclipse might not be able to find the portal anymore. I had the same problem, and the strange thing about it is that IE still connects to the portal.

Smartform debugging problem

Hi Experts,
How to debug smartform in quality. can anybody explain me....
Thanks
rajesh

dear
Do one thing apply the breakpoint in smartform where u r getting the problem and execute directly u will come to that point .
Else execute u will get long string name in function module screen :
Goto to the display mode and then put the break point
this will also do
thanx
-ankit

Debugging problems...

New to PSCS5 is the loss of the 'Hold-the-ALT-key-during-script-launch-to-run-in-ESTK' feature.
This has screwed up my workflow somewhat.
What's worse is that I have now have several PS scripts that won't launch from ESTK at all. They just hang. No error message or anything.
Photoshop pops forward, the ESTK spinner spins, and nothing happens. I have to hit the Stop button and return focus to PS before I can
do anything again with ESTK.
I'll file a bug report now that I'm able to reproduce this with a script I can share with them. But if anybody wants to try to replicate this, download the latest rev of CSX and try and launch it from ESTK. It may be a little sluggish since CSX is flattened out to 25KLOC, but I see the same problem in my dev version that uses //@includes.
As it stands, when ever I want to debug stuff, I have to use "$.level =1; debugger;". I'd really be screwed if that ever went away. Again.

New to PSCS5 is the loss of the 'Hold-the-ALT-key-during-script-launch-to-run-in-ESTK' feature.
This has screwed up my workflow somewhat.
What's worse is that I have now have several PS scripts that won't launch from ESTK at all. They just hang. No error message or anything.
Photoshop pops forward, the ESTK spinner spins, and nothing happens. I have to hit the Stop button and return focus to PS before I can
do anything again with ESTK.
I'll file a bug report now that I'm able to reproduce this with a script I can share with them. But if anybody wants to try to replicate this, download the latest rev of CSX and try and launch it from ESTK. It may be a little sluggish since CSX is flattened out to 25KLOC, but I see the same problem in my dev version that uses //@includes.
As it stands, when ever I want to debug stuff, I have to use "$.level =1; debugger;". I'd really be screwed if that ever went away. Again.

XCode debugging problems

Similar Messages

Maybe you are looking for