Re: [Mingw-w64-public] Mingw toolchains and Clang
Long time ago we add possibility to build Clang into mingw-builds scripts. Now we want to provide Clang builds for mingw-w64 toolchains. There are two possibilities that we can do: *1. *Include clang builds into toolchain archive *2.* Provide separate builds of GCC+Clang I have a question to users what use our toolchains. I want you to vote for the best variant of doing that. I know that some users don't want to have bigger toolchains but I think that in modern time it is not a problem because all drives has big volume. Regards, Alexey. I would like to see a separate build for GCC + Clang, I would also like to know 1) if it is now possible to have 64 bit clang with SEH ? 2) If clang can work with a more recent libstdc++ (say 4.7.2 or 4.8 ? ) 3) most importantly, can we now debug clang compiled code with gdb ? (That was not possible with Ruben's build) I would also like to see 1) some clang tools along with the compiler. like clang-analyzer/ format/modernizer etc ( and include what you want, if possible) 2) debug release libraries for clang llvm, so that one can also use it like Clang C++ SDK to build new tools. Also in long term i like to see ( I hope it is sorter than i think! ) libc++ lldb working on windows, along with some other clang tools like Address Sanitizer, Memory Sanitizer etc Thanks abir -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431iu=/4140/ostg.clktrk ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] GDB version information for ruben vb build (Ruben Van Boxem)
I was using build by Ruben for Mingw W64 for long times with Qt Creator
IDE. However from version 2.7 onward it fails to debug using the gdb
shipped by it. The reason is most likely that it fails to parse the gdb
version information like GNU gdb (rubenvb-4.7.2-release)
7.5.50.20120920-cvs (Or rather wrongly parses the gdb version as 4.7.2
and
disables most of gdb features like python support :( )
My question is , is there any guidelines for what gdb version string
should look like?
I have just tried with
x86_64-w64-mingw32-gcc-4.8.0-win64_rubenvb
Qt Creator 2.7.1
CMake 2.8.11
on a clean system, to create a small test app
#include iostream
using namespace std;
int main()
{
int i=4;
int j= i+4;
i = j-4;
cout Hello World! endl;
return 0;
}
built with
cmake -DCMAKE_BUILD_TYPE=Debug
mingw32-make
and set a break point in Qt Creator at the i=j-4 line, and execution
stopped. I could see the values of i and j displayed.
What exactly are you doing and what fails?
Remember to set up gdb and your toolchain in Tools-Options-BuildRun
both under Compilers and Kits (set your sysroot and click on
auto-detect for the Debugger line).
Hope this helps,
Ruben
I did the same, However debugging does not work :(
What does NOT work =
locals and expressions or stack windows does NOT automatically
load/update on stepping. i.e each time you need to manually click reload
full stack to see the updated values.
Breakpoint stepping does work.
It did work (and still works) with Qt Creator 2.6.2 last, and not any
release after that (i.e QtC 2.7.0, 2.7.1 2.8.0 beta)
All version of QtC also works with mingw builds gdb.
I presently do NOT use mingw builds as sometimes I get strange problems
with that dual target build (specifically when I use it with
boost.unit_test). I do NOT use Qt, I use Qt Creator just for my c++
projects with cmake or generic makefile project.
In the debugger log window it shows UNSUPPORTED GDB VERSION GNU gdb
(rubenvb-4.8.0) 7.5.91.20130322-cvs
If you look at the code which detect gdb version (extractGdbVersion
in debuggerprotocol.cpp ) , it returns wrong gdb version as 4.8.0 rather
than 7.5.91 , i.e. wrongly takes the version from bracketed gcc build
information). Though that may or may not be the cause of problem.
I have tested it with
x86_64-w64-mingw32-gcc-4.8.0-win64_rubenvb.7z (and also 4.7.2 and others)
QtC 2.7.1 (Build on 8th May 2013) QtC 2.7.0 and QtC 2.8.0 beta official
builds
On Windows 7 and Windows 8
Thanks
abir
--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with 2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] GDB version information for ruben vb build (Ruben Van Boxem) (Ruben Van Boxem)
It seems clear to me that you should submit a patch that fixes this to Qt Project, and also if possible file the boost unit_test issue with the mingw-builds project. I took the liberty to submit a bug report to the Qt Project: https://bugreports.qt-project.org/browse/QTCREATORBUG-9452 If any Qt guys are reading this, I'll be very happy if this is bumped to anywhere but the bottom of the stack ;-) Thanks for filing the bug report. Though the problem is not specific to Mingw w64, I asked it this mailing list as Qt Creator mailing list suggested ask the person providing that GDB build to not patch the version string, or at least to not deviate too much from what other distributions do Thanks abir Cheers, Ruben -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] GDB version information for ruben vb build
I was using build by Ruben for Mingw W64 for long times with Qt Creator IDE. However from version 2.7 onward it fails to debug using the gdb shipped by it. The reason is most likely that it fails to parse the gdb version information like GNU gdb (rubenvb-4.7.2-release) 7.5.50.20120920-cvs (Or rather wrongly parses the gdb version as 4.7.2 and disables most of gdb features like python support :( ) My question is , is there any guidelines for what gdb version string should look like? Thanks abir -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] Clang 64bit
If I understand correctly, according to Ruben Van Boxem clang 64 bit compiler on windows can not be used for compilation as exception handling is broken. Also Ruben had clarified that clang 32 bit windows debug information is also useless and it can not be used to debug a program, though linking using gcc/ld will work just fine. I recently notices that Embarcadero C++ Builder XE 3 64bit (the previous Borland C++ Builder) uses clang as compiler instead of their own. It has its own linker, but according to their documentation it generates ELF64 object file with DWARF debug information, and MS 64bit calling convention. Their clang triple is x86_64-pc-win32-elf and is based on llvm3.1 svn Assuming they are using clang not just for parsing, but for code generation also, how they managed to have a 64bit working clang compiler, and also working DWARF debug information? -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
[Mingw-w64-public] Debugging Clang 3.2 rubenvb build
If I want to debug an executable created with clang 3.2 rubenvb build, it shows DW_FORM_strp pointing outside .debug_str section The gdb version comes with the build GNU gdb (rubenvb-4.6.3-2-release) 7.5.50.20121228-cvs Is there any way I can debug an application compiled with clang 3.2 ? Thank you -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
