I'm writing a debugger for VSCode, is it possible to see what is going into and coming out of the debugger in VSC?
I thought stdout was going to be echoed to the Debug Console, but even with a simple application that writes a message and closes nothing appears.
Ideally I'd like to see everything including DAP messages? Is this available anywhere?
Related
Hello guys i am new to programming and i just installed vs code, everything is working fine except when i run the code the console comes and goes without me even seeing the output.So how do i make it stay. or how do i run the output inside the vs code terminal and just eliminate that pop up console.
The thing is i need to take screenshots of the output for my lecturer to see for future projects. Attached is a screenshot.the console is only here because it needs inputhere after input it just disappears
I am trying to debug in chrome dev tool. My form shows some weird validation error when I type something into the input field and then quickly click somewhere outside the field. I found the browser debugger is not able to catch my last click behavior and it becomes very difficult to debug where things go wrong. Is there a way to slow down the debugger's reaction?
When I uncheck "Preserve log" in the console settings, I don't see the error below. Why are they related?
When Preserve Log is enabled, the Console preserves messages until you explicitly clear it. When it's disabled, the Console clears messages on page loads.
So, it looks like there's some code that runs just before you navigate to a new page, and that code is throwing an error. So while the error technically does get displayed (for a split-second) in both scenarios, it's probably just getting erased before you can see it with your eyes when you have Preserve Log disabled.
With Pry (but also with Rubymine), I'm trying to debug a certain point in the code (using binding.pry). After calling Capybara's save_screenshot, I'm unable to execute any Capybara related commands (all commands die on time-out). This works out of a "debug mode" and in other web-drivers like Poltergeist.
I took a couple of hours today trying to debug it. I think I found the problem - or at least a way around it.
Our web site has a couple of links that open content in another browser window. Since the automation is quite ancient, and in that time Selenium didn't have a decent way to switch window-context, what we do is to visit the opened page by URL, and by this keep only a single window open at any given time.
This works, but something strange happens when running this test on "debug mode" (using binding.pry for example). Right before we do any actions on that specific page, we take a screen-shot using Capybara's save_screenshot method. On debug this results a corrupted image, and any following Capybara methods will fail on time-out. Opening this page using the link, and handling the windows context switching with Capybara's handle_window method solves the issue. It's still a mystery why it only happens with Capybara wekit though (as other web-drivers work properly). I'm guessing that perhaps the DOM might be structured differently.
I am developing in PHP with Xdebug and for some reason every now and then the debug session stops working, so i click again the debug button but it gives me this error all the time "Web launch already running", so i have to go to Debug Perspective and click "Terminate and Relaunch".
Is there a way to make eclipse automatically terminate and relaunch or launch two sessions or don't show this popup, for 2 years this popup has been bugging me xD
As noted in response to questions like this one and this one, the best current solution appears to be binding "Terminate and Relaunch" to a keyboard shortcut.
Not automatic, but at least a lot less clicking around.
I have taken care of pesky popups in Eclipse with AutoHotkey script which have worked very well. I could create an AutoHotkey script which sends specific keystrokes automatically every time there is a specific pop-up.
So the flow I had in mind was as follows :
You click on the debug button -> The Error popup appears and as soon as that happens the AutoHotKey script kicks in and automatically does what you have to do manually.
If you think that might be worth looking into then we can talk more in a Chat session somewhere. I would need some information about the Pop up using the AU3_Spy.exe bundled with the AutoHotkey Installer.
Searching on Google, I found that many people have the same problem.
Bellow are some links that help you, I think:
https://aptanastudio.tenderapp.com/discussions/questions/123-definitive-installation-guide-for-php-debugging-on-linuxubuntu
A good article: http://www.latenightpc.com/blog/archives/2008/05/24/a-complete-lamp-development-environment-xampp-eclipse-pdt-and-xdebug
See this, too: http://www.eclipse.org/forums/index.php/m/57493/
Take a look here, too: Getting error in XDEBUG
So, read and try, read and try.