Re: [Mingw-w64-public] GDB version information for ruben vb build (Ruben Van Boxem)
03.06.2013, в 12:56, Abir Basak abirba...@gmail.com написал(а): 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. Try our single target builds. They are DWARF and SEH: x32-4.8.1-release-posix-dwarf-rev0.7z x64-4.8.1-release-posix-seh-rev0.7z-- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j___ 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)
03.06.2013, в 12:56, Abir Basak abirba...@gmail.com написал(а): 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. Try our single target builds. They are DWARF and SEH: x32-4.8.1-release-posix-dwarf-rev0.7z x64-4.8.1-release-posix-seh-rev0.7z-- How ServiceNow helps IT people transform IT departments: 1. A cloud service to automate IT design, transition and operations 2. Dashboards that offer high-level views of enterprise services 3. A single system of record for all IT processes http://p.sf.net/sfu/servicenow-d2d-j___ 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)
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.
On Mon, Jun 3, 2013 at 9:56 AM, Abir Basak abirba...@gmail.com wrote:
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
--
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)
2013/6/3 Ray Donnelly mingw.andr...@gmail.com
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 ;-)
Cheers,
Ruben
On Mon, Jun 3, 2013 at 9:56 AM, Abir Basak abirba...@gmail.com wrote:
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
--
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
--
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
