2013-05-17 Joel Brobecker <brobecker@adacore.com>
+ * lynx-low.c (lynx_resume): Fix null_ptid/minus_one_ptid
+ confusion in comment.
+
+2013-05-17 Joel Brobecker <brobecker@adacore.com>
+
* lynx-low.c (struct process_info_private): New type.
(lynx_add_process): New function.
(lynx_create_inferior, lynx_attach): Replace calls to
? PTRACE_SINGLESTEP : PTRACE_CONT);
const int signal = resume_info[0].sig;
- /* If given a null_ptid, then try using the current_process'
+ /* If given a minus_one_ptid, then try using the current_process'
private->last_wait_event_ptid. On most LynxOS versions,
using any of the process' thread works well enough, but
LynxOS 178 is a little more sensitive, and triggers some
if (ptid_equal (ptid, minus_one_ptid))
ptid = current_process()->private->last_wait_event_ptid;
- /* The ptid might still be NULL; this can happen between the moment
- we create the inferior or attach to a process, and the moment
- we resume its execution for the first time. It is fine to
- use the current_inferior's ptid in those cases. */
+ /* The ptid might still be minus_one_ptid; this can happen between
+ the moment we create the inferior or attach to a process, and
+ the moment we resume its execution for the first time. It is
+ fine to use the current_inferior's ptid in those cases. */
if (ptid_equal (ptid, minus_one_ptid))
ptid = thread_to_gdb_id (current_inferior);