[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-debug-dev] What's the "Working directory" in theLaunch Config UI ?
|
John, I cann't agree more.
As to the UI, as we can hardly find a standard way of
telling whether it's remote debug or local, I think it will be up to each debug
implementation (product provider) to subclass or create its own ArgumentTab
and distinguish between remote and local in its own way. In other words,
the CArgumentTab from CDT & DSF should just be used as a
reference.
- Ling
Ling, for sure the working directory preference should represent the
WD of the program being debugged. Any treatment of it a anything else seems like
a bug to me and should be fixed. If we need a similar pref for gdb, then that
should go in the Debugger tab.
As for whether it makes sense for the LC
to allow the user to navigate to a local directory: the answer is yes, and no.
Yes, if debugging locally; no if debugging remotely. If there's a way to
distinguish within the LC UI, then the
Workspace and
File
System... buttons should be disabled. So, e.g., for a JTAG LC, those buttons
should be disabled. But I suspect that's the best we can do. In a standard LC,
what would we use as criteria for knowing it's a "remote" session. Even with
gdbserver as the selected debugger, you could conceivably be debugging an
executable running on the host.
John
At 01:18 PM 9/9/2008,
Ling.5.Wang@xxxxxxxxx wrote:
Hi, there,
This seems like a
basic issue that's not clearly defined.
In the CDT (and DSF) launch
configuration preference panel "Arguments"
(internally CArgumentTab), there
is the "Working directory" option. My
question is, what is that option
supposed to mean, working directory of
the debugger (e.g. gdb), or that of
the debugged program ?
For local debug, the difference usually does
not matter much. But for
remote debug, the working directory of the
debugged program should be a
dir on remote device/machine, while the
working directory of the
debugger is on host PC.
>From the source
code I can see that it's treated as working dir for
debugger.
But
the UI is ambiguous. "arguments" are surely for debugged program, so
user
would take it for granted that the "working directory" there is for
his
program, though actually it's not.
Actually for a user, what he cares
about is the working directory of his
program, not the debugger. But the UI
(the "browse" buttons, and the
validator that checks if the directory
exists on host PC) requires that
the working directory to be on host PC,
which impose a problem for
remote debug.
So I think we should first
decide on what the "working directory" should
be, and then decide on what
to change about UI.
-
Ling
_______________________________________________
cdt-debug-dev
mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
