This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
target_signal_from_host => gdb_signal_from_host (or gdb_signal_from_host_signal) target_signal_to_host => gdb_signal_to_host (or gdb_signal_to_host_signal)
gdbarch_target_signal_from_host => gdbarch_gdb_signal_from_target (or gdbarch_gdb_signal_from_target_signal) gdbarch_target_signal_to_host => gdbarch_gdb_signal_to_target (or gdbarch_gdb_signal_to_target_signal)
OK, but I'd recommend target_signal_from_host => gdb_signal_from_target target_signal_to_host => gdb_signal_to_target
This is symmetric with the gdbarch_ functions and clear that the function translates to/from target system values, not the host system.
But it's not what the functions do... They really convert from the host system signals, not the target's. I think the symmetry will only lead to people getting confused (which one to call in common/target-independent code?).
If you are running GDB on a Windows host, for example, what host system signals are you translating?
-- Michael Eager eager@eagercon.com 1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |