<div class="gmail_quote">2011/3/9 Michel Dänzer <span dir="ltr"><<a href="mailto:daenzer@debian.org">daenzer@debian.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Die, 2011-03-08 at 22:00 +0000, Thue Janus Kristensen wrote:<br>
><br>
> With both drmDropMaster breakpointed in the second server,<br>
> and drmSetMaster breakpointed in the first server, drmDropMaster is<br>
> called first in the second server, and the first server doesn't reach<br>
> drmSetMaster until after I continue the second server from the<br>
> drmDropMaster breakpoint. No crash.<br>
><br>
><br>
> With only drmSetMaster breakpointed in the first server, but the<br>
> second server still running with gdb attached for consistency, there<br>
> is no crash when I continue the first server from the drmSetMaster<br>
> breakpoint.<br>
><br>
><br>
> With both servers running inside gdb, but no breakpoints, it crashes.<br>
<br>
</div>So, apparently the problem is that drmSetMaster runs 'too early'...<br>
<br>
How about if you only set a breakpoint on drmDropMaster in the second<br>
server, and on hitting it just 'finish' the function before continuing.<br>
Does the first server hit drmSetMaster before drmDropMaster has finished<br>
in the second one?<br></blockquote><div><br></div><div>No. Nothing happens even after I "finish" in the second server. Only when I continue after the drmDropMaster "finish", does the first server hit the drmSetMaster breakpoint (or crash if there is no drmSetMaster breakpoint).</div>
<div><br></div><div>Regards, Thue</div></div>