VS2005 debugger disassembly window - debugging

I use PB 6.0 to debug my Windows-CE image. Whenever I run in this mode VS2005 opens the disassembly window each time it hits a debug break in a file that it does not have its source (pdb file for the module). This is really annoying as I would like to stick to the output view. I could find a setting to disable this disassembly window automatic opening. Tools->options->debugging->general-> deselecting "show disassembly if source is not available" did not help.
My question:
Does anyone know how to disable this disassembly window automatic activation?
Thanks,
Shai

goto Visual Studio Menu in that Select Tools => Option => Debugging => General
and uncheck the Show Disassembly if source is not available
it will disable DisAssemble at bebug time
i
think it will work fine
Ajay Patel

Related

Set a breakpoint in an attached process that is not started yet - VS

I'm trying to debug an executable (.exe) using Visual-Studio (2019). I opened a new solution and added a command contains the path of my exe, as describes in here How do I attach Visual Studio to a process that is not started yet?.
Because of I'm interesting at the first instructions it executes, I want to set a data breakpoint /breakpoint in a specific adress that I've found on the disass window .
when running the solution and hitting the 'Break all' option, I could view the disassembly window, and then I've found the location that I want to break at. When I placed there a breakpoint and restarted, it seemed that the breakpoint was marked off.
How can I achieve that?
Here is what I've tryed so far:
Playing around with the Debugger type window (Solution => properties => debugging => Debugging type)
Open a new solutio, and try it there
Any help would be much appreciated!
You can open the exe in VS like you would a project/solution. From the VS menu use File->Open Project/Solution and select the .exe file you want to debug. This will create an 'exe project'. You can launch it with F5, to pause on the 'first' statement you can launch with F10 instead. Then when you set breakpoints if you save the solution they should be persisted for when you next launch the exe. You'll need symbols and source for the exe if you're to make much sense of when you debug though.

IntelliJ IDEA 2017 - Missing Debug window

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

How do I turn debugging in disassembly off permanently?

Whilst debugging a console app in c# and VS2008, disassembly window appears uninvited.
I am debugging my code line by line using F11. I have break points set and it starts off well then after a call in a method to open database connection, the debugger opens disassembly window and stays there. I have right-clicked on disassembly tab and selected hide but the window pops again as soon as I hit F11.
How do I turn debugging in disassembly off permanently?
Go to Debug->Options and Settings, uncheck the box for Enable address-level debugging and that should do what you want.
You also may want to check Enable Just My Code if it is not checked.

How to turn off showing assembly codes when debug?

I accidentially turn on this mode and want to return to previous setting. How can I do this?
Not sure about VS2010, but in VS 2008 Go to Tools->Options->Debugging->General and uncheck Show disassembly if source is not available.
Tools->Options->Debugging->General-> Uncheck "Enable address-level debugging->Show disassembly if source not available"
All debugging options are in the Debug menu => Option & Settings. Could you explain your issue a little more precisely?
Either way, look at the different options available here, in the Debugging tab.
I believe you can turn it off in the same way that you turned it on:
On the Debug menu, choose Windows, and click Disassembly.

Visual Studio switches from disassembler to source each time I step

On one of my two computers I see following behaviour:
Each time I press F10 (Step over) or F11 (Step Into) in the disassembler window, the focus is switched to the source view, resulting in next F10 / F11 done on the source level unless I switch focus back.
Can anyone recommend me what settings to inspect, or what to try to stay in the disassembler view?
Did you try to reset settings on your VS?
from the Visual Studio command prompt window type devenv /ResetSettings
Look in the Tools > Options > Environment > Keyboard section, and check what F10/F11 are currently assigned to (although I can't believe it's something that simple)
Copying the settings from the working computer might solve it. You don't mention what version you're running, but I think they're in the same location in 2005 onwards : My Documents\Visual Studio 2005\Settings\CurrentSettings.vssettings. There's always the Import and Export Settings Wizard too.
Try setting a breakpoint in the assembly view. I'm assuming the existing breakpoints are in the source view.
Could it perhaps be: Tools->Options->Debugging->Enable address-level debugging?
I just tried in VS05, and when I have that unchecked, I can't even bring up the disassembly view, but I would guess that if you somehow got into disassembly view, having that option off would kick you out of disassembly view when you did a step over/into.
Close the source file window ? I had the inverse problem that cause F11 to always debug in assembly, it was fixed by closing the assembly window. May be it works in reverse too ?
Not sure, if this would work but... try if you can?
Open RegEdit
Browse to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet
Explorer -> Main
Add a DWORD under this key called TabProcGrowth
Set TabProcGrowth to 0 (zero)
This is what I used when VS2005 debug mode stopped working (0:
Try removing any .pdb files from the directory you are executing from. Also make sure your Options->Debugging->Symbols settings aren't pointing to any pdbs for the files in question.
Of course I'm assuming you've been through all the other Options->Debugging options, including the native section.

Resources