It seems my old thread on this went to sleep, and since now I am posting a solution to a problem rather than the problem itself, I hope noone minds if I start a new thread...
My original problem was that while I could successfully compile with Cygwin, I could not use Dev (4.9.8.0) to debug (I didn't get any blue line).
Since I have a lot of pre-compiled libs (blas, lapack, nag, gsl) in Cygwin, I was hoping to solve the problem short of having to recompile them with Mingw.
Now it turns out that the solution is rather simple: I just installed Mingw and borrowed its gdb.exe, copied it into cygwin\bin under a new name, and told Dev to debug using this version of gdb. But I still compile with Cygwin.
According to the Dev homepage, "Dev-C++ can also be used in combination with Cygwin", which thus is only partially true, unless one applies this tweak. This could therefore be useful info for a lot of people out there!
However, including support for the Cygwin gdb is probably simple, since as far as I can judge the only (?) difference compared to the Mingw gdb is the output end-of-lines, which appear to be Unix-style for Cygwin but Dos-style for Mingw.
If you are not yet bored with my long posting, let me point out a potential bug in 4.9.8.0. In the debug output (where I see what gdb is saying), I am supposed to be able to right-click and choose Copy or Clear, right? Well, both options are greyed out, always.
Anders
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using Dev-C++ to develop code for the Palm using the Cygwin/pilrc tools. The code generation works fine. The debugging using POSE does not work. I can get the link between Dev-C++, m68k-palmos-gdb and POSE working but the debugger responses are not interpreted correctly - presumably because of the problem mentioned in this thread. I haven't yet found a Mingw code suite for Palm so I cannot use this tweak.
I searched the Dev-C++ mailing list and forum and found that the Cygwin debugger problem bug report is now cleared/deleted. Is there a possibility that the problem will be addressed sometime or is there some other tweak which can be used to get the Cygwin debugger going?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems my old thread on this went to sleep, and since now I am posting a solution to a problem rather than the problem itself, I hope noone minds if I start a new thread...
My original problem was that while I could successfully compile with Cygwin, I could not use Dev (4.9.8.0) to debug (I didn't get any blue line).
Since I have a lot of pre-compiled libs (blas, lapack, nag, gsl) in Cygwin, I was hoping to solve the problem short of having to recompile them with Mingw.
Now it turns out that the solution is rather simple: I just installed Mingw and borrowed its gdb.exe, copied it into cygwin\bin under a new name, and told Dev to debug using this version of gdb. But I still compile with Cygwin.
According to the Dev homepage, "Dev-C++ can also be used in combination with Cygwin", which thus is only partially true, unless one applies this tweak. This could therefore be useful info for a lot of people out there!
However, including support for the Cygwin gdb is probably simple, since as far as I can judge the only (?) difference compared to the Mingw gdb is the output end-of-lines, which appear to be Unix-style for Cygwin but Dos-style for Mingw.
If you are not yet bored with my long posting, let me point out a potential bug in 4.9.8.0. In the debug output (where I see what gdb is saying), I am supposed to be able to right-click and choose Copy or Clear, right? Well, both options are greyed out, always.
Anders
bump, some Cygwin users might have re-interest....or would that be compound interest...
Wayne
I am using Dev-C++ to develop code for the Palm using the Cygwin/pilrc tools. The code generation works fine. The debugging using POSE does not work. I can get the link between Dev-C++, m68k-palmos-gdb and POSE working but the debugger responses are not interpreted correctly - presumably because of the problem mentioned in this thread. I haven't yet found a Mingw code suite for Palm so I cannot use this tweak.
I searched the Dev-C++ mailing list and forum and found that the Cygwin debugger problem bug report is now cleared/deleted. Is there a possibility that the problem will be addressed sometime or is there some other tweak which can be used to get the Cygwin debugger going?