<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 6, 2019, at 2:11 PM, Joshua Peraza <<a href="mailto:jperaza@google.com" class="">jperaza@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Adding a hashes where we need them SGTM.<div class=""><br class=""></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 4, 2019 at 10:31 AM Greg Clayton <<a href="mailto:clayborg@gmail.com" class="">clayborg@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class="">If it is inside the object itself, and we have only 1 user data "void *" per object, I can see many clients wanting to use this user data. </div></blockquote><div class=""><br class=""></div><div class="">This surprised me though. There are situations where multiple clients are using LLDB simultaneously? </div></div></div>
</div></blockquote><br class=""></div><div>The embedded Python interpreter and the IDE or command line that are running LLDB are two I can think of. Also if the baton lives in the lldb_private::* objects, then we can have internal clients as well as clients through the API.</div><br class=""></body></html>