[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [dsdp-dd-dev] New type of launch discussion
|
> I like option 1 assuming it is "attach to an application". But the
> problem is how to get the list of processes running on the remote
> target.
The exact name I was thinking of using was
"C/C++ Attach to Running Application"
As for the list of processes, it was suggested on the GDB list to
add this support to gdbserver and I'm hoping there will be a patch
for GDB 6.9. Until then, I suggest the user be prompted for a
pid without having a list to choose from.
Marc
-----Original Message-----
From: dsdp-dd-dev-bounces@xxxxxxxxxxx
[mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
Sent: Thursday, May 08, 2008 4:17 PM
To: Device Debugging developer discussions
Subject: RE: [dsdp-dd-dev] New type of launch discussion
> Originally we had two only launch configurations "Local" and "Core".
> "Attach" was an option of the "Local" launch configuration, as you are
> suggesting. That wasn't very intuitive and we had had many complains.
> There were also some technical problems, so we decided to add a
special launcher.
Thanks, that is important to know. So maybe keeping "local" and "attach
to local"
separate is important. DSF-GDB also has a separate "remote" launch.
And eventually, there will be "core".
In our meetings, with toyed with the following options:
1- Changing "attach to local" to simply "attach" and to let the user
specify the target,
which could be localhost.
2- Add an attach option to the "remote" launch (which seems to have been
your approach
as well for "local")
3- Add a 5th configuration type "attach to remote running application".
Since your experience has proved that adding an attach option to a
launch didn't seem to please users, I guess it is better to keep the
concept of attaching separate, so we can ignore option 2/
My guess is that the "attach" launch is not the most commonly used
anyway, so maybe making it slightly more complex is ok. So I vote for
option 1 (at least for now.)
How does that sound?
Marc
_______________________________________________
dsdp-dd-dev mailing list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
dsdp-dd-dev mailing list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
