<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 Jun 18, 2019, at 7:08 AM, Romaric Jodin via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hello everyone,<div class=""><br class=""></div><div class="">I am trying to add a new architecture into LLDB.</div><div class="">My architecture is a accelerator with its own ISA for which we have a LLVM backend (release 7.1).</div><div class=""><br class=""></div><div class="">I have started by creating a new NativeProcessProtocol for my architecture. So I have a lldb-server that run on a x86, but which takes care of process of my architecture. I have forced it to use my NativeProcessProtocol.</div><div class="">I have a issue with this method because as the lldb-server is compile to run on a x86, some part of the code think that it is managing x86 process.</div></div></div></blockquote></div><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Maybe I am going in the wrong direction to add such new architecture to LLDB, I would be happy to try any other suggestions.</div></div></div></blockquote><div><br class=""></div><div>lldb-server is currently meant to build a native debugging GDB server that can be used with lldb. If you want to always build a cross build lldb-server for your architecture, you will want to add a new tool that gets built in the CMakeList.txt in the tools/lldb-server directory. You will need to build it into a different binary like "lldb-server-dpu". I am not sure how much trouble you will run into doing this though as much of the lldb-server build assumes things match the current host.</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><br class=""></div><div class="">If you are interested, you can have a look at my branch "dev/rjodin/lldb_dpu" in our forked repo of LLDB "<a href="https://github.com/upmem/lldb" class="">https://github.com/upmem/lldb</a>". The branch is not clean, but it can help you understand what I did.</div><div class=""><br class=""></div><div class="">Thanks,</div>-- <br class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div style="color:rgb(136,136,136)" class=""><span style="font-size: 12.8px;" class=""><b class="">Romaric JODIN</b></span></div><div style="color:rgb(136,136,136)" class=""><span style="font-size: 12.8px;" class="">UPMEM</span></div><div style="color:rgb(136,136,136)" class=""><font size="1" class=""><i class="">Software Engineer</i></font></div><div style="color:rgb(136,136,136)" class=""><br class=""></div><div style="color:rgb(136,136,136)" class=""><span id="cid:ii_jm7vnlj17_165ed4ff64757184"><logo signature mail 50x50.png></span></div></div></div></div></div>
_______________________________________________<br class="">lldb-dev mailing list<br class=""><a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev<br class=""></div></blockquote></div><br class=""></body></html>