look at the screenshot at https://snipboard.io/9lWtnp.jpg - it shows
my current state of Komodo. I don't know how I arrived there and my
problem is: How do I get back a menu where I can run / debug a
program?
I remember having a toolbar with the usual buttons for run /
step over / step into etc., but somehow I managed to lose it and am
unable to get it back.
Help, please.
M'
Problem solved: The 'alt' key seems to toggle the menu in and out of sight. Once in sight, in the debug menu I can click on Go/Continue and debugging starts - and even the debug toolbar appears at the bottom.
M'
Related
My Intellij Debugger window went missing and I can't find any resources on how to get it back, the closest think I can get to my problem is a missing console window but that doesn't help. So I'm hoping someone here can help me retrieve it.
This pic shows a normal Intellij IDE (that I got from my friend) that shows the tab that's missing for me (in red) and the area in which this tab normally shows (in yellow).
And this pic shows my IDE with the missing Debugger window.
I also opened Intellij's help dialogue which claims that the window will show up when your code hits a break point but that didn't do it for me either.
Try the "restore layout" button at the left toolbar of the debugger toolwindow
Showing a tool window:
"Choose View" | "Tool Windows" | "Debug Tool Window" in the main menu.
It as simple as that.
There are multiple other things you can try, look here:
https://www.jetbrains.com/help/idea/manipulating-the-tool-windows.html#show
For example reset your Tool Windows:
You can return to the default workspace layout by choosing "Window" | "Restore Default Layout" (Shift+F12).
To enable the debug window
Click on View -> Tool Windows -> Debug
Or press (Alt+5)
This is not an answer to the specific question asked but a possible solution to My debug window has disappeared!. My situation was actually with Android Studio but should apply elsewhere.
My symptoms were:
I use multiple monitors and after a system crash my debug window
vanished.
Before the crash my debug window was in window mode on a separate
monitor. After the crash it was gone.
There was no Debug tab showing on the main window.
The Debug entry in the View menu was greyed.
The solution that finally worked was to set a break-point at a location I knew the code would hit, debug my project and make it hit the break-point. The Debug window magically appeared.
Remember to reposition the window correctly before exiting.
Try button on the right (there should be debugger, console....)
Try to Restore default layout in console/debugger screen. Its give in image please do check.
Remove the dev option from run/debug configurations from Command line.
You would have undocked, just look for "dock" sign, click on it.
Now debugger will restored to default view
I am aware that command + ' brings you to the next issue, but is there a way to bring you to the next compiler error and ignore the warnings?
(xcode 9)
I don't think there is a way to do that, but the closest thing you could do to that is to filter the display of issues in the Issue Navigator so it only shows errors and no warnings. Do that with one click, on the icon at the bottom right of the Issue Navigator.
Once you have done that, then the up and down arrow keys navigate you within the Issue Navigator from error to error instead of issue to issue.
To expand on auspicious99's answer, after filtering on errors in the issues pane, you can use keyboard shortcuts end to end:
cmd-5 - selects the issues pane
up/down arrows - select the error you want
cmd-j, enter - move the focus to the editor
In the navigator (the left-hand pane), choose the right-most icon that looks like a speech bubble. You'll see the build results, and when you click on them you'll be taken to the error.
I was happily printlning to the Console Output in the Assistant Editor of a Swift/Xcode 6 Playground (see this SO thread for more info), until I decided to try clicking the [X] to close the Console Output.
How do I bring the Console Output back??
This eluded me for a while, too. You want View menu -> Assistant Editor -> Show Assistant Editor.
Once you see the pane that holds the console output, if you still aren't seeing the right thing, make any change that will cause a println() to fire and the console output should appear.
Just hover your mouse pointer over the value evaluation area (pane next to your coding area) and click on the plus sign to open the output pane. If you have closed the console output in the output pane, then click anywhere in the coding area and press enter. You will get your console output back.
If the View > Assistant Editor > Show Assistant Editor does not work, simple go to the bottom of the screen and drag the little footer up, so it looks like so:
Closing the Playground and reopening did not bring the Console Output back, but quitting Xcode and reopening did. If there's an answer that doesn't require restarting Xcode I'll go for that, but for now this seems to be the answer :/
Yay for beta software!
You can bring back the console frame by following the steps below:
Open the assistant editor. In the assistant editor, find the playground timeline screen.
In the playground timeline screen, find the bottom right corner box, where it contains "- 31 +" (In my case it says the time elapsed is 31; it can differ according to your code).
Click the "+" / "-" mark in the "- 31 +" box.
There your result, console frame along with the other frames could have come there.
The keyboard shortcut is Cmd + Shift + Y
If you've opened the Assistant editor, either by using Cmd+Option+Enter, or selecting the white/plus icon on the left of a line, and then removed the "Console output" there are some alternatives which may help you in getting it back:
Make sure you don't have any errors in your playground, as they stop execution and thusly any output to the Assistant Editor
Make a change so that playground is re-executed
Force a new run of the playground using Editor > Execute Playground
Change the timer in the lower right, as this also triggers a new run of the playground
Restart Xcode as the playground is a little buggy, and you sometimes just need to restart everything... :-(
Put a /* at the top line of your code area to comment out everything. The Console Output box will reappear at the top of the right-hand panel (the Assistant editor panel).
Some errors may show in the Console box. Ignore.
Now delete the /* and the Console box will stay put.
have just started xcode (version 7.0.1) using swift but had the same problem, to show how the code will appear in console I toggled the little triangle next to the play button on the bottom left of the screen
triangle toggle button
this then open a view in which I could see the results of the code
console opend
hope this helps
There seems to be a a series of problems related to using the keyboard (only) on the mac - as opposed to resorting to the mouse. I am wondering if people have figured out workarounds for some of these issues.
Example 1: Hitting Enter does not work. Hitting tab does not work.Hitting space does not work. Only way to 'accept'/close the dialog is to mouse over and hit ok. Yuck.
Example 2: Using The Option button we can the "Do Refactor has D underlined - so clicking option-D should accept. However it does not work. Once again - only way is to click using the mouse
Example 3: In refactor dialog, one can not hit "return" or tab over or use "alt-r" to accept the Refactor. Once again - using mouse is the only way.
Example 4: In ANY open file dialog you have to type in manually the entire path. This one is confirmed bug by JetBrains, and I wonder if anyone has an idea of workaround
Click on the "option" key and the Mnemonics DO show up. I discovered this by accident.
this was the answer from the brad larson on this
SO question
If you add two breakpoints, you should be able to debug these exceptions. To do this, go to Run | Show | Breakpoints and create two global breakpoints (I do them globally because they are so useful in all my applications). The first should be named "objc_exception_throw" and its location should be "libobjc.A.dylib". The second should be "-[NSException raise]" and its location should be "CoreFoundation".
Now, if you start debugging your application with breakpoints enabled, it should break on the throw of these exceptions. You should then be able to see the chain of events that led to the exception within the debugger.
now in this answer i want to ask how do i add location mentioned???
I think Brad's answer is pretty clear; hopefully this can help if you're not finding it clear.
In Xcode, from the top menu click on Run > Show > Breakpoints. A new window pops up.
Select "global breakpoints" in the left hand menu. There should be a box on the right under the "Breakpoint" column with the text "Double-Click for symbol". Single-click in this box and type in "objc_exception_throw".
Then, single-click in the space next to "objc_exception_throw" under the "location" column. A box will appear for you to type in the location (in this case, "libobjc.A.dylib"). I've made a screenshot that will hopefully help:
In Xcode 4 this great breakpoint can be added via "+" button on Breakpoints section (⌘ + 6)
in Xcode 6 -- from top menu
Debug > Breakpoints > Create Exception Breakpoint
I would also like to recommend adding the +[NSException raise:format:arguments:] breakpoint and its location should be CoreFoundation.