I build GDB for ARM from GDDBSources(GDB7.5) using MinGW and MSYS for windows.But sometimes while connecting GDB to the QEMU , GDB crash occurs with a message :
"gdb.exe has stopped working" in windows7.
What is the solution of this issue?
I had the same situation before. The solution is using mingw-w64 in place of MinGW in windows 7. It works well for me.
Related
I recently installed Ubuntu 18.04 LTS, for the Windows Subsystem For Linux (WSL).
I installed a large number of packages, including ubuntu-desktop, build-essential, qtcreator and a number of others.
QTCreator itself seems to work fine for the most part. I can compile projects and run them in both Debug and Release just fine.
However, when I try to enter "Start Debugging" in a debug release, it hangs indefinitely. Once started, "stop debugging" does not work anymore, and the only fix is to completely kill QTCreator and restart it. Same thing happens on a coworkers machine.
Is this a known limitation of WSL?
Emacs + GDB seems to fine for debugging, so it shouldn't be an issue with GDB which I believe QTCreator uses under the hood. (Though for various reasons, I still want QTCreator's debugger specifically)
Ubuntu 18.04 LTS
GDB is version (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git
Windows 10 is build 1909
QTCreator is version 4.5.2, based on QT 5.9.5
Using VcXsrv Windows X Server
I recently moved from Java to C++, and experiment using Eclipse CDT. I created a HelloWorld project, which compiled and run fine.
I then tried to enable the debugger, but couldn't get it running properly. Below is my debugger configuration (I am using gdb in Mac Sierra, gdb installed using homebrew, codesigned already). Please advice what additional setting I might need to do in order to get debugger work. Thank you!
I get the pop up "Failed to start terminal for debugger".i have set the gdb path in the gdb options of codelite. Is there anything else to be done?
My mac os version is 10.10.4
GDB version installed under /usr/local/bin/gdb - version 7.8.1
The c project created a simple hello world to test the codelite usage on mac os and unfortunately not able to launch gdb.The compilation is going through fine
On OSX, the recommended the debugger is LLDB.
Please use it instead.
Project settings->general->Debugger, and select "LLDB Debugger"
EDIT, Sep 06:
I have uploaded a new OSX build (8.2.3) with this problem fixed.
http://codelite.org/support.php
The Symbian S60 Toolchain isn't available for Linux, it's Windows only. I downloaded the Windows installer for Qt Creator and just ran it under Wine. The install went mostly fine, except 'simulator.exe -registeronly' failed, and now the IDE shows and works OK, but when I try to compile for S60, I get:
:-1: error: [release-gcce] Error 2 (File not found)
Update
I tried something else. Some files were missing from the Wine installation, so I copied the entire QtSDK directory from a Windows install. Now the compilation produces a .sis file which can be installed on my phone, but when I try to run the application it won't start. It shows the busy cursor equivalent in Symbian for some time, but then terminates before actually showing a window. On the other hand, .sis files created with the same QtSDK from the Windows machine install and run fine.
I've just installed Ocaml on Mac OS X, and when I run the ocaml program I get a "Bus Error" with no other clues to what might be going on. Can anyone offer suggestions on where to go from here?
EDIT:
I installed via the package:
http://caml.inria.fr/pub/distrib/ocaml-3.10/ocaml-3.10.2-ppc.dmg
(I have an iBook G4, so PPC is appropriate)
To run ocaml, I just typed:
ocaml
in a terminal window
I also tried
/usr/local/bin/ocaml
and running from an xterm window. All three give:
Bus Error
I have Xcode and X11 installed as the README requires.
Turns out I was installing a version of OCaml built for Mac OS X 10.5.x (Leopard) on my machine running 10.4.x (Tiger). One would think it would be easy for the installer to catch this, but alas...
Did you install it from macports? It's working fine for me. Can you describe some more details about your installation? Perhaps what you're doing to get the error?