I can no longer set breakpoint in Eclipse Version: Neon.3 Release (4.6.3),
Build id: 20170314-1500, MinGW_64 (Posix) on Windows 10 (64bits) in the last
2 days on any C++ programs including a simple Hello World below:
#include<iostream>usingnamespacestd;intmain(){cout<<"!!!Hello World!!!"<<endl;// tried to set breakpoint on this linereturn0;}
This program & others runs fine in Eclipse.
The debug error are as follows:
GNU gdb (GDB) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word". [New Thread 3728.0x1f40] [New Thread 3728.0x1354] [New Thread 3728.0xdb4]
Warning:
Cannot insert breakpoint 1.
Cannot access memory at address 0x75af355b
Not sure whether it is related to the following informative message after successful project built:
"Info: Configuration "Debug" uses tool-chain "MinGW GCC" that is unsupported on this system, attempting to build anyway."
Re-installing MinGW_64 (Posix) failed to make a difference. I
wouldn't mind re-installing Eclipse but not sure whether it will make any
difference & how to do it. Also not sure whether I should use the mINgw_64 (Win32) version instead.
The following Windows environment variables have been set:
MinGW_HOME=C:\MingW\mingw32;
PATH=C:\MingW\mingw32\bin;
These variables are set in Eclipse Preferences,C/C++,Build,Environment variable
I have been informed by other forums that this issue is to do with MinGW-64 compiler, as opposed to an Eclipse IDE one.
I couldn't find recent post on this issue & would appreciate any advice after
having spent days on trying to fix it without success.
This feature was working after initial installation earlier last week.
Thanks in advance,
George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is this an active forum? Are there any moderator monitoring any post? Is
there anything I have missed or am I posting to the wrong forum altogether?
I like to continue using MinGW-64 but may need to look at other product if
no community support is available.
Any assitance or guidance would be much appreciated.
Thanks,
George
Hello George,
that gdb issue is something I can't reproduce, and I assume other
people on this forum can't too. So it might be related to the place
where you got this gdb build (or eclipse package) from.
We are trying to help people in general, but this report is not really
something we could solve AFAICS.
Anyway, if you could explain in more details, there might be somebody
being able to give you further help.
Regards,
Kai
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I managed to removed MinGW64 and remove Eclipse Neon C++ IDE in the extracted folder C:\Software Development\Download\eclipse-cpp-neon-3-win32-x86_64\eclipse followed by reboot Windows 10.
I then extracted Eclipse to C:\Software Development\eclipse-cpp-neon-3-win32-x86_64\eclipse and install MinGW using the correct installer from www.mingw.org successfully.
Have also updated MINGW_HOME=C:\MinGW and PATH=C:\MinGW\bin on Windows environment variables and in Eclipse Preference C/C++ Build Environment.
Both Eclipse & MinGW are working except the step into / over (F5/F6) debugger function are not available / active, even though it does stop at the breakpoint that was set. The only option available in is to terminate the Hello World program.
Have I missed anything else.
Any assistance would be appreciated before I give up using this product and just buy VS2017 that does not have any of these hassles.
Thanks,
George
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear MinGW-64 C++ Specialists,
I can no longer set breakpoint in Eclipse Version: Neon.3 Release (4.6.3),
Build id: 20170314-1500, MinGW_64 (Posix) on Windows 10 (64bits) in the last
2 days on any C++ programs including a simple Hello World below:
This program & others runs fine in Eclipse.
The debug error are as follows:
GNU gdb (GDB) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word".
[New Thread 3728.0x1f40]
[New Thread 3728.0x1354]
[New Thread 3728.0xdb4]
Warning:
Cannot insert breakpoint 1.
Cannot access memory at address 0x75af355b
Not sure whether it is related to the following informative message after successful project built:
"Info: Configuration "Debug" uses tool-chain "MinGW GCC" that is unsupported on this system, attempting to build anyway."
Re-installing MinGW_64 (Posix) failed to make a difference. I
wouldn't mind re-installing Eclipse but not sure whether it will make any
difference & how to do it. Also not sure whether I should use the mINgw_64 (Win32) version instead.
The following Windows environment variables have been set:
MinGW_HOME=C:\MingW\mingw32;
PATH=C:\MingW\mingw32\bin;
These variables are set in Eclipse Preferences,C/C++,Build,Environment variable
I have been informed by other forums that this issue is to do with MinGW-64 compiler, as opposed to an Eclipse IDE one.
I couldn't find recent post on this issue & would appreciate any advice after
having spent days on trying to fix it without success.
This feature was working after initial installation earlier last week.
Thanks in advance,
George
Is this an active forum? Are there any moderator monitoring any post? Is there anything I have missed or am I posting to the wrong forum altogether?
I like to continue using MinGW-64 but may need to look at other product if no community support is available.
Any assitance or guidance would be much appreciated.
Thanks,
George
2017-05-29 15:00 GMT+02:00 George Jackson netbeansfan@users.sf.net:
Hello George,
that gdb issue is something I can't reproduce, and I assume other
people on this forum can't too. So it might be related to the place
where you got this gdb build (or eclipse package) from.
We are trying to help people in general, but this report is not really
something we could solve AFAICS.
Anyway, if you could explain in more details, there might be somebody
being able to give you further help.
Regards,
Kai
Thanks Kai Tietz for trying,
I managed to removed MinGW64 and remove Eclipse Neon C++ IDE in the extracted folder C:\Software Development\Download\eclipse-cpp-neon-3-win32-x86_64\eclipse followed by reboot Windows 10.
I then extracted Eclipse to C:\Software Development\eclipse-cpp-neon-3-win32-x86_64\eclipse and install MinGW using the correct installer from www.mingw.org successfully.
Have also updated MINGW_HOME=C:\MinGW and PATH=C:\MinGW\bin on Windows environment variables and in Eclipse Preference C/C++ Build Environment.
Both Eclipse & MinGW are working except the step into / over (F5/F6) debugger function are not available / active, even though it does stop at the breakpoint that was set. The only option available in is to terminate the Hello World program.
Have I missed anything else.
Any assistance would be appreciated before I give up using this product and just buy VS2017 that does not have any of these hassles.
Thanks,
George