<div dir="ltr">I don't see a problem with that. There is a ton of basic functionality not working there yet but will be coming online soonish. I was limiting it to just Linux x86_64 to simplify the initial bring-up, but now that I have a FreeBSD VM, this is probably a good sanity check to make sure I won't have too much work to bring it up in other environments.<div>
<br></div><div>So feel free to turn it on for FreeBSD.</div><div><br></div><div>> <span style="font-family:arial,sans-serif;font-size:13px">This is the assert (g_swig_init_callback != NULL) in</span></div><span style="font-family:arial,sans-serif;font-size:13px">ScriptInterpreterPython.cpp?</span><div>
<font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Nah - it's an issue with the current default Host process launching on Linux (and maybe FreeBSD?) that doesn't seem to be able to launch a process in a stopped state. So there's an assert in the posix launch that verifies the launch flag doesn't ask for starting the process in a stopped state. (Not so helpful for a debugger, eh? ;-) ). I think this problem will go away when I start bridging over to launching processes correctly soon here. For the moment you'll see that Linux masks out the launch flag for launch in a debugged state. Obviously we do this right for local debugging, so I'll be adjusting this code soon. <br>
</font><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 5, 2014 at 8:49 AM, Ed Maste <span dir="ltr"><<a href="mailto:emaste@freebsd.org" target="_blank">emaste@freebsd.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 15 January 2014 20:25, Todd Fiala <<a href="mailto:tfiala@google.com">tfiala@google.com</a>> wrote:<br>
> Hi all,<br>
><br>
> I'm finally getting some cycles to put on lldb-gdbserver for x86_64 linux.<br>
><br>
> I created a dummy looping exe (never exits), ran lldb_gdbserver against it<br>
> in a terminal on my (local) x86_64 Ubuntu 12.04, turned on all logging, and<br>
> attached from the (local) x86_64 Ubuntu 12.04 with top of tree as of<br>
> yesterday. My only diffs at the moment are enabling lldb-gdbserver to build<br>
> under linux and x86_64, and commenting out an assert that doesn't seem to<br>
> make sense that always hits when starting up lldb-gdbserver.<br>
<br>
</div>This is the assert (g_swig_init_callback != NULL) in<br>
ScriptInterpreterPython.cpp? After removing that and adding the<br>
subdirectory to tools/CMakeLists.txt I can build and run<br>
lldb-gdbserver on FreeBSD, and a basic sanity test works fine (e.g.,<br>
target create /bin/ls, b main, run, c).<br>
<br>
> ...<br>
<div class="im">> I'll start digging into these. I'll flip on building of lldb-gdbserver for<br>
> x86_64 as soon as I have it doing anything more than just the above.<br>
<br>
</div>I'd be happy to have it added to the default build now (or once the<br>
assert is sorted out) - I don't see a downside beyond a trivial amount<br>
of extra build time.<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><table cellspacing="0" cellpadding="0" style="color:rgb(136,136,136);font-family:'Times New Roman'"><tbody><tr style="color:rgb(85,85,85);font-family:sans-serif;font-size:small">
<td nowrap style="border-top-style:solid;border-top-color:rgb(213,15,37);border-top-width:2px">Todd Fiala |</td><td nowrap style="border-top-style:solid;border-top-color:rgb(51,105,232);border-top-width:2px"> Software Engineer |</td>
<td nowrap style="border-top-style:solid;border-top-color:rgb(0,153,57);border-top-width:2px"> <a href="mailto:tfiala@google.com" style="color:rgb(17,85,204)" target="_blank"><span style="background-color:rgb(255,255,204);color:rgb(34,34,34);background-repeat:initial initial">tfiala@google.com</span></a> |</td>
<td nowrap style="border-top-style:solid;border-top-color:rgb(238,178,17);border-top-width:2px"><font color="#1155cc"> <a>650-943-3180</a></font></td></tr></tbody></table><br></div>
</div>