This is the mail archive of the gdb-prs@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]

[Bug threads/19471] unexpected stop in multi-inferior debugging


https://sourceware.org/bugzilla/show_bug.cgi?id=19471

--- Comment #6 from Tom Tromey <tromey at sourceware dot org> ---
That was the wrong patch, but it has the bits from the earlier missing
patch in the context, so you can reconstruct it ok from there.

Anyway, that patch causes an assertion failure if you also
"set schedule-multiple on".  The new call to target_resume(RESUME_ALL,...)
calls down to linux-nat.c, ending up in x86_linux_update_debug_registers,
which does 

  gdb_assert (lwp_is_stopped (lwp));

I am not sure how this code is intended to work.
Like, I would have thought that the "target_resume" call would do the
right thing; that is, that the backends would take care to only resume
things which are resumable.  So, maybe I could fix this in linux_nat_resume...
but if this isn't generally how targets are supposed to work, then 
maybe the correct fix is in the caller, to have it only resume threads
that are not already running.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]