Menu
▾
▴
#303 Cross development issues
It won't accept an executable with no extension (like
you have on Linux). It always add exe.
You can't do remote debugging (e.g. with gdbserver). To
be able to do this you need to be able to specify an
initialisation file for gdb, which runs a set of commands
before Dev-C++ does its commands. In such a file you
can re-difine the 'run' command to connect to the
remote server, download the file (if appropriate) and
continue execution.
This would be very handy to have, and would match the
functionality of Eclipse (dog slow and resource hungry)
and KDevelop (on Linux only).
Logged In: YES
user_id=609236
this functionality was never implemented in dev-c++, so
those are more feature requests then bugs. Do you agree?
Logged In: YES
user_id=487598
Yes.
However, it should be simple to implement. Add an extra text
(file chooser) field to the Debug->Parameters... dialog
called 'gdb initialisation file' and pass this as an option to gdb
when invoking.
There are of course implications. The CPU window is tied to
the x86 and if you do remote debugging, there's nothing to
say you have an x86 the other end. When you do 'info reg' on
gdb it lists the register names and values, so you could
dynamically set up the register boxes in accordance with
what is returned.
Regarding the CPU window, someone is bound to suggest that
it should be under the debug tab at the bottom, rather than a
separate window.
Someone will also ask if there can be a memory window (with
a box at the top to enter the symbol or address, and a box
below showing values, displayable as 8, 16, or 32-bit words
with/without ascii in a separate column).
I would say, on the debug tab, which
has "Debug", "Backtrace" and "Output",
add "Dissassembly", "Registers" and "Memory".
Regarding the disassembly, people at some point will ask for
mixed source and dissassembly display.
I'm saying these latter things, because people will compare
Dec-C++ with Visual Studio and other tools which have the
features I've just described. I'm aware that intregrated
debugging is a new addition to Dev-C++.
Logged In: YES
user_id=487598
One thing I forgot to mention - there are 4 stepping
operations in gdb: step, next, and stepi, nexti. There seems
to be some confusion between instruction stepping and
source code line stepping.