From: "Marc Weustink" <[EMAIL PROTECTED]>
Yury Sidorov wrote:
From: "Marc Weustink" <[EMAIL PROTECTED]>
Yury Sidorov wrote:
From: "Vincent Snijders" <[EMAIL PROTECTED]>
Yury Sidorov wrote:
[snip]
4. Lazarus should have an ability to specify debugger settings for
each target CPU/OS.
I do not understand this, please elaborate.
At least debugger type and debugger path need to be configurable for
each target.
For example I use one win32\gdb.exe for debugging win32 apps and use
win32-arm\gdb.exe for remotely debugging wince apps.
Therefore different debuggers must be called for different targets.
afaik you can use the same gdb for it (but Iv'e to admit that I never
have used a remote gdb)
No. gdb for WinCE is absolutely different build. It can be used only to
debug WinCE applications.
That's why several different debuggers need to be configured at the same
time.
For example:
1. Win32 native gdb.
2. WinCE remote debugger.
3. Linux debugger via SSH.
4. MacOS debugger via SSH.
5. ... etc.
Once configured they will be used automatically when you run a project
for corresponding target.
I think this is more a project option then something based on a target.
On linux I want sometimes to debug locally and sometimes remote, depending
on what project I'm working with.
Sure. It will be great to have an ability to choose debugger and set some
its options per project. But there should be default set of debuggers also.
Now I see it as follows:
An ability to add several debugger configurations in global debugger
options. For each configuration target CPU and target OS specified.
For every project needed debugger configuration is used if found matched
CPU/OS pair.
Also it will be good manually choose needed debugger configuration in
project options.
Yury Sidorov.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
