To debug chromium using gdb (LinuxDebugging) one can use
chromium --renderer-cmd-prefix="gdb --args"
and
chromium --plugin-launcher="gdb --args"
Chromium then launches debugger with "gdb --args" and pass command line specifying how to launch that process. Then I can use gdb from command line as normally.
How can I achieve the same scenario in Eclipse?
By using non-stop mode I can debug chrome as usual. But since renderer and plugins are running out of process, I can't track them.
Eclipse can be used on Linux as an IDE for developing Chromium. This is from official google link:
http://code.google.com/p/chromium/wiki/LinuxEclipseDev
The only solution I've found is "attach to process" approach.
Update: seems like Eclipse Indigo (gdb 7.2) supports multiprocess debugging.
Didn't try it yet.
I don't recall anyone on the Chromium uses Eclipse with Chrome for debugging. With that technique, you can only use gdb.
Eclipse is not a supported environment, if you can support it, it would be super :)
Use Qtcreator to debug chrome on linux, you need to just attach the process.
Related
I could not debug using goclipse plugin, it was asking about gdb debugger then I downloaded the binary ver. 7.6 but now it is giving me "Source Not found"..
As suggest from many posts, I tried to build the program before going to start debugging but still it is giving me the same thing.
below is a secreenshot
even I found some guys were saying is to specify the working directory in configuration as "other" but still giving me the same error
finally, I fixed the issue by using the "gdb" distributed within liteide package. you could reference it from "Window | Preferences"
Hey there I've been using the JetBrains IDE support extension for a week now, and While it is great utility. I grow tired of clicking the "X' in the Chrome Yellow Warning ("JetBrains IDE Support" is debugging this tab.)
This may be a noobish question for experienced devs, but does anyone knows how to get rid of this Chrome pop-ups?
Thanks :)
Here is a snapshot:
You can disable this warning in chrome://flags using the Enable Silent Debugging flag:
It's mentioned in the comment #28.
Here is the direct link to the option:
chrome://flags/#silent-debugger-extension-api Just paste this to your Chrome addressbar.
For the ones who didn't understand ( like me :P )
You need to open this address chrome://flags in Google-Chrome and Enable Silent Debugging
While the relevant flag has been removed from chrome://flags, you can still use the command line switch:
chrome --silent-debugger-extension-api
which can be persisted in your flags config (eg. ~/.config/chrome-flags.conf on linux).
See Enable Silent Debugging is not available in Chrome browser
For the newer versions of the Chrome this flag is not available anymore.
So Here is the solution
Open settings in your IDE then head into Tools>Web Browsers
then click on Chrome and hit the pencil icon and
write this in "command line options" finaly hit ok
--silent-debugger-extension-api
now close your chrome if it is open then try to launch it again using debug or run...
I have am trying to debug some PHPunit tests in netbeans, but it doesn't stop at my break-points.
I can, however, debug the site in the browser and it stops at my breakpoints.
I have modified file->project properties->run configuration->advanced to "do not open web browser".
I use the following script to initiate phpunit :
export XDEBUG_CONFIG="idekey=netbeans-xdebug";
phpunit $#
What could be the problem?
ps. I have had it working in the past, but it stopped working and I had to reinstall xdebug. I am using ubuntu 11.10
Thanks.
This usually happens when your port is not set to listen on xdebug's default listener port 9000.
Here's some instructions on mac for netbeans but it should do the trick even if you're running windows.
http://netbeans.org/kb/docs/php/configure-php-environment-mac-os.html
I am using nsight eclipse edition for mac to debug my cuda code. I was able to run cuda-gdb all fine from a terminal but was not able to use the debug function in Nsight. Whenever I started to debug, an error window pops up saying "Error in final launch sequence
Connection is shut down". My OS is Mac Lion (10.7.4).
I understand the big thing in Cuda 5.0 is the interactive debugging with eclipse but sadly I won't be able to use it unless I switch to Windows or Linux. If anybody has seen this or knows a workaround for this, please let me know and your help will be very much appreciated.
Thank you!
I'm afraid you've hit a known issue in CUDA 5.0 Toolkit. Due to some last-minute change, cuda-gdb (which is a shell script) is not entirely valid in Mac OS X. To remedy the problem:
Edit cuda-gdb shell script.
Make line #!/bin/sh the first line in this script.
Save the changes
We apologize for inconvenience. This (and many other) issues will be fixed in the upcoming CUDA 5.0 RC release.
I had this problem in linux recently.
Error in final launch sequence Connection is shut down which means nsight can not start debugger correctly.
first you have to make sure you can run cuda-gdb in terminal. just type cuda-gdb in terminal, if it says like cuda-gdb cannot find some lib in /usr/lib, just download or relink it. after you done this , rerun cuda-gdb in terminal, it should work fine. then you can use nsight debugging tool.
I just got this MSI wind netbook and tried to run eclipse on it. I installed JDK6 on the netbook already. Whenever I open eclipse there is nothing show up on the screen except a "warning sound" that alerts. What is the problem here?
ps.I just started learning java.
Most likely the Eclipse starter program can't find where you installed Java. Since Eclipse is a Java program, it needs a JRE installed (comes with the JDK typically) to run. Assuming you're running Windows on your MSI Wind, check to make sure the java executable is on your path in your computer environment settings (windows key + printscreen button, or windows key + pause button are the shortcuts to open the computer properties dialog if I remember correctly. Then go to advanced).
You can test if java is on the path by opening a cmd.exe shell window and typing 'java'. If it says it cannot find java, then you need to fix the path.
See this link for additional troubleshooting details: http://www.eclipsezone.com/eclipse/forums/t99010.html
You could try reinstalling the JDK. Perhaps having it on a different disk than the default (D: versus C:) is causing some trouble? It certainly isn't a problem with the hardware, I'm running Eclipse on Windows on an MSI Wind.
Use "Add/Remove programs" in the control panel to remove the java versions you have installed.
Then visit "java.com" and use it to install Java, and verify that it is working. You do not need more than that to use Eclipse.