Re: [lldb-dev] Passing as argument an array in a function call
Hi,
it turned out to be due to a local change in my repository, where I've forced Process::CanJIT() to be always evaluated, to track down a different unrelated issue, instead of using m_can_jit. Restoring
the original semantic resolved my issue. I can now imagine that CanJIT() interfered with the memory already allocated in the device.
I am sorry for this oversight :/
Thanks,
Dean
On 16/12/15 19:29, Tamas Berghammer wrote:
I verified and LLDB also works correctly in case of arm and aarch64 on android
(using lldb-server). My guess is that it is a MIPS specific but in the SysV ABI
but I haven't verified it.
Tamas
On Wed, Dec 16, 2015 at 6:37 PM Greg Clayton via lldb-dev mailto:lldb-dev@lists.llvm.org>> wrote:
> On Dec 16, 2015, at 6:06 AM, Dean De Leo via lldb-dev mailto:lldb-dev@lists.llvm.org>> wrote:
>
> Hi,
>
> assume we wish to use the expression evaluator to invoke a function from
lldb, setting the result into an array passed as parameter, e.g:
>
> void test1(uint32_t* d) {
>for(int i = 0; i < 6; i++){
>d[i] = 42 + i;
>}
> }
>
> where the expected output should be d = {42,43,44,45,46,47}. However
performing the following expression having as target android/mips32 returns:
>
> (lldb) expr -- uint32_t data[6] = {}; test1(data); data
> (uint32_t [6]) $4 = ([0] = 0, [1] = 2003456944, [2] = 44, [3] = 45, [4]
= 2004491136, [5] = 47)
>
> Is this an expected behaviour or a bug?
Definitely a bug in LLDB somewhere, or possibly in the memory allocation on
the MIPS host that is done via lldb-server. Are you using lldb-server here? It
has an allocate memory packet.
> I suspect the evaluator allocates the memory for data and releases once
the expression has been executed?
We allocate memory for the resulting data that continues to exist in your
process so the memory shouldn't be released.
> If so, can you please advise what's the proper way to achieve the same
functionality?
This should work so it will be a matter of tracking down what is actually
failing. If you can run to where you want to run your expression and then
before you run your expression do:
(lldb) log enable -f /tmp/log.txt gdb-remote packets
(lldb) log enable -f /tmp/log.txt lldb expr
Then run your expression and then do:
(lldb) log disable gdb-remote packets
(lldb) log disable lldb expr
Then send the file, we might be able to see what is going on. The GDB remote packets
will allow us to see the memory that is allocated, and the "lldb expr" will
allow us to see all of the gory
details as to where it is trying to use "d".
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] r255887 - TestGlobalVariables.py
Hi Ewan! r255887 has broken the tests on OS X for the dwarf version of that test. Can you please either fix it to work on OS X, or revert the change? I'm not interested in disabling that test on OS X since it covers important functionality. Thank you! Now that the test rerun support is in, I'll be able to turn on the test runner portion of the OS X buildbot soon so this would have been more obvious. You can also mark https://llvm.org/bugs/show_bug.cgi?id=25872 that I filed yesterday with whichever you do. -- -Todd ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25872] OS X: TestGlobalVariables dwarf is not finding the static const int g_file_static_int
https://llvm.org/bugs/show_bug.cgi?id=25872 Todd Fiala changed: What|Removed |Added Assignee|lldb-dev@lists.llvm.org |clayb...@gmail.com --- Comment #1 from Todd Fiala --- We're going to try to fix this. -- You are receiving this mail because: You are the assignee for the bug. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] r255887 - TestGlobalVariables.py
Hi Ewan, Scratch that. I started poking at it with Greg and we're going to try to fix this over here. I will temporarily mark as XFAIL on Darwin. You have no action to take here. Thanks! -Todd On Fri, Dec 18, 2015 at 9:47 AM, Todd Fiala wrote: > Hi Ewan! > > r255887 has broken the tests on OS X for the dwarf version of that test. > Can you please either fix it to work on OS X, or revert the change? I'm > not interested in disabling that test on OS X since it covers important > functionality. > > Thank you! > > Now that the test rerun support is in, I'll be able to turn on the test > runner portion of the OS X buildbot soon so this would have been more > obvious. > > You can also mark https://llvm.org/bugs/show_bug.cgi?id=25872 that I > filed yesterday with whichever you do. > -- > -Todd > -- -Todd ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] building on mac
Are the Xcode scripts using the llvm configure build? If so they will need to be changed to the CMake build sooner or later, because the configure build is going away in the near future. On Thu, Dec 17, 2015 at 3:18 PM Todd Fiala via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Ah. > > Okay, this might be the llvm/clang build script that Xcode uses as an > llvm/clang build step. That's going to need to be updated if it is using > configure (for the reasons I mentioned above). > > So it sounds like some part of llvm or clang may be sniffing and finding > some part of ocaml, and deciding it should make some bindings for it. I'll > have a look at the script and see if there's an obvious way to explicitly > deny it (the warning seemed like it had a way to disable that binding, so > we might just need to work it in). > > Of course, if you are not using ocaml, you might want to consider > removing/hiding it if you don't need it. > > Interestingly, I did have ocaml on my home system a while back and didn't > have any trouble building, but I probably had ounit2 as well, and likely > wouldn't have noticed if the Xcode-based build-llvm script ended up doing > more work when building the embedded llvm/clang during the Xcode build. > > I can probably replicate this pretty easily. > > On Thu, Dec 17, 2015 at 3:10 PM, Ryan Brown wrote: > >> Does xcode use configure? I just push command-B. >> It does look like I have ocaml installed on my system, but I'm not sure >> how it go installed or why xcode is trying to use it. >> >> -- Ryan Brown >> >> On Thu, Dec 17, 2015 at 2:54 PM, Todd Fiala wrote: >> >>> We definitely should not be requiring ocaml :-) >>> >>> Are you using a configure-based build? If so, can you switch over to >>> using cmake and see if you see that same issue? We pretty much don't >>> maintain the configure build, and it is getting stripped from llvm and >>> clang in the next version of them after 3.8, so we will not be able to >>> support configure-based builds in the near future. >>> >>> In the event that you still see it, let us know if you have ocaml or >>> opam somewhere on your system. The warnings do seem to indicate that ocaml >>> was specified for one reason or another? Maybe parts of it were sniffed >>> out when trying to configure the build. >>> >>> -Todd >>> >>> On Thu, Dec 17, 2015 at 1:36 PM, Ryan Brown via lldb-dev < >>> lldb-dev@lists.llvm.org> wrote: >>> Are there new prereqs for building on a mac? I just updated, and I'm getting this error: checking for __dso_handle... yes configure: WARNING: --enable-bindings=ocaml specified, but ctypes is not installed configure: WARNING: --enable-bindings=ocaml specified, but OUnit 2 is not installed. Tests will not run configure: error: Prequisites for bindings not satisfied. Fix them or use configure --disable-bindings. error: making llvm and clang child exited with value 2 -- Ryan Brown ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >>> >>> >>> -- >>> -Todd >>> >> >> > > > -- > -Todd > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] building on mac
Right: "Okay, this might be the llvm/clang build script that Xcode uses as an llvm/clang build step. That's going to need to be updated if it is using configure (for the reasons I mentioned above)." On Fri, Dec 18, 2015 at 10:26 AM, Zachary Turner wrote: > Are the Xcode scripts using the llvm configure build? If so they will > need to be changed to the CMake build sooner or later, because the > configure build is going away in the near future. > > On Thu, Dec 17, 2015 at 3:18 PM Todd Fiala via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> Ah. >> >> Okay, this might be the llvm/clang build script that Xcode uses as an >> llvm/clang build step. That's going to need to be updated if it is using >> configure (for the reasons I mentioned above). >> >> So it sounds like some part of llvm or clang may be sniffing and finding >> some part of ocaml, and deciding it should make some bindings for it. I'll >> have a look at the script and see if there's an obvious way to explicitly >> deny it (the warning seemed like it had a way to disable that binding, so >> we might just need to work it in). >> >> Of course, if you are not using ocaml, you might want to consider >> removing/hiding it if you don't need it. >> >> Interestingly, I did have ocaml on my home system a while back and didn't >> have any trouble building, but I probably had ounit2 as well, and likely >> wouldn't have noticed if the Xcode-based build-llvm script ended up doing >> more work when building the embedded llvm/clang during the Xcode build. >> >> I can probably replicate this pretty easily. >> >> On Thu, Dec 17, 2015 at 3:10 PM, Ryan Brown wrote: >> >>> Does xcode use configure? I just push command-B. >>> It does look like I have ocaml installed on my system, but I'm not sure >>> how it go installed or why xcode is trying to use it. >>> >>> -- Ryan Brown >>> >>> On Thu, Dec 17, 2015 at 2:54 PM, Todd Fiala >>> wrote: >>> We definitely should not be requiring ocaml :-) Are you using a configure-based build? If so, can you switch over to using cmake and see if you see that same issue? We pretty much don't maintain the configure build, and it is getting stripped from llvm and clang in the next version of them after 3.8, so we will not be able to support configure-based builds in the near future. In the event that you still see it, let us know if you have ocaml or opam somewhere on your system. The warnings do seem to indicate that ocaml was specified for one reason or another? Maybe parts of it were sniffed out when trying to configure the build. -Todd On Thu, Dec 17, 2015 at 1:36 PM, Ryan Brown via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Are there new prereqs for building on a mac? > I just updated, and I'm getting this error: > > checking for __dso_handle... yes > > configure: WARNING: --enable-bindings=ocaml specified, but ctypes is > not installed > > configure: WARNING: --enable-bindings=ocaml specified, but OUnit 2 is > not installed. Tests will not run > > configure: error: Prequisites for bindings not satisfied. Fix them or > use configure --disable-bindings. > > error: making llvm and clang child exited with value 2 > > > -- Ryan Brown > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > -- -Todd >>> >>> >> >> >> -- >> -Todd >> ___ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> > -- -Todd ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] building on mac
Where do I find the script xcode is using? -- Ryan Brown On Fri, Dec 18, 2015 at 12:42 PM, Todd Fiala wrote: > Right: > > "Okay, this might be the llvm/clang build script that Xcode uses as an > llvm/clang build step. That's going to need to be updated if it is using > configure (for the reasons I mentioned above)." > > > > On Fri, Dec 18, 2015 at 10:26 AM, Zachary Turner > wrote: > >> Are the Xcode scripts using the llvm configure build? If so they will >> need to be changed to the CMake build sooner or later, because the >> configure build is going away in the near future. >> >> On Thu, Dec 17, 2015 at 3:18 PM Todd Fiala via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >>> Ah. >>> >>> Okay, this might be the llvm/clang build script that Xcode uses as an >>> llvm/clang build step. That's going to need to be updated if it is using >>> configure (for the reasons I mentioned above). >>> >>> So it sounds like some part of llvm or clang may be sniffing and finding >>> some part of ocaml, and deciding it should make some bindings for it. I'll >>> have a look at the script and see if there's an obvious way to explicitly >>> deny it (the warning seemed like it had a way to disable that binding, so >>> we might just need to work it in). >>> >>> Of course, if you are not using ocaml, you might want to consider >>> removing/hiding it if you don't need it. >>> >>> Interestingly, I did have ocaml on my home system a while back and >>> didn't have any trouble building, but I probably had ounit2 as well, and >>> likely wouldn't have noticed if the Xcode-based build-llvm script ended up >>> doing more work when building the embedded llvm/clang during the Xcode >>> build. >>> >>> I can probably replicate this pretty easily. >>> >>> On Thu, Dec 17, 2015 at 3:10 PM, Ryan Brown wrote: >>> Does xcode use configure? I just push command-B. It does look like I have ocaml installed on my system, but I'm not sure how it go installed or why xcode is trying to use it. -- Ryan Brown On Thu, Dec 17, 2015 at 2:54 PM, Todd Fiala wrote: > We definitely should not be requiring ocaml :-) > > Are you using a configure-based build? If so, can you switch over to > using cmake and see if you see that same issue? We pretty much don't > maintain the configure build, and it is getting stripped from llvm and > clang in the next version of them after 3.8, so we will not be able to > support configure-based builds in the near future. > > In the event that you still see it, let us know if you have ocaml or > opam somewhere on your system. The warnings do seem to indicate that > ocaml > was specified for one reason or another? Maybe parts of it were sniffed > out when trying to configure the build. > > -Todd > > On Thu, Dec 17, 2015 at 1:36 PM, Ryan Brown via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> Are there new prereqs for building on a mac? >> I just updated, and I'm getting this error: >> >> checking for __dso_handle... yes >> >> configure: WARNING: --enable-bindings=ocaml specified, but ctypes is >> not installed >> >> configure: WARNING: --enable-bindings=ocaml specified, but OUnit 2 is >> not installed. Tests will not run >> >> configure: error: Prequisites for bindings not satisfied. Fix them or >> use configure --disable-bindings. >> >> error: making llvm and clang child exited with value 2 >> >> >> -- Ryan Brown >> >> ___ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> >> > > > -- > -Todd > >>> >>> >>> -- >>> -Todd >>> ___ >>> lldb-dev mailing list >>> lldb-dev@lists.llvm.org >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >>> >> > > > -- > -Todd > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] turning on tests for OS X llvm.org Green Dragon builder
Hi all, I'm working on turning this on soon here (sometime this afternoon). It is possible that we'll see a bit of noise as I get it going. If we get erroneous output from the builder while I get this settled, I'll be sure to post on that email thread. I'll send out a "it's really on" email once it is both on and working. It'll be running both the gtests (C++ unit tests) and the LLDB Python test suite. -- -Todd ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] building on mac
Hi Ryan! I talked to Sean Callanan about this. We think the real fix is probably tracking down why llvm/clang are thinking it is okay to assume we want to use the ocaml bindings without actually saying we want to use them. Anything we do on our end looks like it would be a hack to avoid a broken script. If you just want to work around this temporarily, you can either install the other ocaml bits (I think the message said it was the unit test framework) or uninstall ocaml. But to answer your question, Xcode uses this Perl script (ancient): scripts/build-llvm.pl -Todd On Fri, Dec 18, 2015 at 12:44 PM, Ryan Brown wrote: > Where do I find the script xcode is using? > > -- Ryan Brown > > On Fri, Dec 18, 2015 at 12:42 PM, Todd Fiala wrote: > >> Right: >> >> "Okay, this might be the llvm/clang build script that Xcode uses as an >> llvm/clang build step. That's going to need to be updated if it is using >> configure (for the reasons I mentioned above)." >> >> >> >> On Fri, Dec 18, 2015 at 10:26 AM, Zachary Turner >> wrote: >> >>> Are the Xcode scripts using the llvm configure build? If so they will >>> need to be changed to the CMake build sooner or later, because the >>> configure build is going away in the near future. >>> >>> On Thu, Dec 17, 2015 at 3:18 PM Todd Fiala via lldb-dev < >>> lldb-dev@lists.llvm.org> wrote: >>> Ah. Okay, this might be the llvm/clang build script that Xcode uses as an llvm/clang build step. That's going to need to be updated if it is using configure (for the reasons I mentioned above). So it sounds like some part of llvm or clang may be sniffing and finding some part of ocaml, and deciding it should make some bindings for it. I'll have a look at the script and see if there's an obvious way to explicitly deny it (the warning seemed like it had a way to disable that binding, so we might just need to work it in). Of course, if you are not using ocaml, you might want to consider removing/hiding it if you don't need it. Interestingly, I did have ocaml on my home system a while back and didn't have any trouble building, but I probably had ounit2 as well, and likely wouldn't have noticed if the Xcode-based build-llvm script ended up doing more work when building the embedded llvm/clang during the Xcode build. I can probably replicate this pretty easily. On Thu, Dec 17, 2015 at 3:10 PM, Ryan Brown wrote: > Does xcode use configure? I just push command-B. > It does look like I have ocaml installed on my system, but I'm not > sure how it go installed or why xcode is trying to use it. > > -- Ryan Brown > > On Thu, Dec 17, 2015 at 2:54 PM, Todd Fiala > wrote: > >> We definitely should not be requiring ocaml :-) >> >> Are you using a configure-based build? If so, can you switch over to >> using cmake and see if you see that same issue? We pretty much don't >> maintain the configure build, and it is getting stripped from llvm and >> clang in the next version of them after 3.8, so we will not be able to >> support configure-based builds in the near future. >> >> In the event that you still see it, let us know if you have ocaml or >> opam somewhere on your system. The warnings do seem to indicate that >> ocaml >> was specified for one reason or another? Maybe parts of it were sniffed >> out when trying to configure the build. >> >> -Todd >> >> On Thu, Dec 17, 2015 at 1:36 PM, Ryan Brown via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >>> Are there new prereqs for building on a mac? >>> I just updated, and I'm getting this error: >>> >>> checking for __dso_handle... yes >>> >>> configure: WARNING: --enable-bindings=ocaml specified, but ctypes is >>> not installed >>> >>> configure: WARNING: --enable-bindings=ocaml specified, but OUnit 2 >>> is not installed. Tests will not run >>> >>> configure: error: Prequisites for bindings not satisfied. Fix them >>> or use configure --disable-bindings. >>> >>> error: making llvm and clang child exited with value 2 >>> >>> >>> -- Ryan Brown >>> >>> ___ >>> lldb-dev mailing list >>> lldb-dev@lists.llvm.org >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >>> >>> >> >> >> -- >> -Todd >> > > -- -Todd ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >>> >> >> >> -- >> -Todd >> > > -- -Todd ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] turning on tests for OS X llvm.org Green Dragon builder
Still in progress. I've got the tests running, but I've still got some configuration issues to work out to get them running cleanly. On Fri, Dec 18, 2015 at 12:48 PM, Todd Fiala wrote: > Hi all, > > I'm working on turning this on soon here (sometime this afternoon). It is > possible that we'll see a bit of noise as I get it going. If we get > erroneous output from the builder while I get this settled, I'll be sure to > post on that email thread. > > I'll send out a "it's really on" email once it is both on and working. > > It'll be running both the gtests (C++ unit tests) and the LLDB Python test > suite. > -- > -Todd > -- -Todd ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] turning on tests for OS X llvm.org Green Dragon builder
Hi all, This is complete. We now have OS X running the tests (both gtest and Python tests) at the end of the build phase on the LLVM Green Dragon OS X build. This build: http://lab.llvm.org:8080/green/view/LLDB/job/LLDB/15459/ is the first build where I got everything working. It already sends nag emails to the authors of any changes when it first switches state to a broken state. And, now, broken will include broken gtests or broken Python tests in addition to build breaks. -Todd On Fri, Dec 18, 2015 at 3:45 PM, Todd Fiala wrote: > Still in progress. I've got the tests running, but I've still got some > configuration issues to work out to get them running cleanly. > > On Fri, Dec 18, 2015 at 12:48 PM, Todd Fiala wrote: > >> Hi all, >> >> I'm working on turning this on soon here (sometime this afternoon). It >> is possible that we'll see a bit of noise as I get it going. If we get >> erroneous output from the builder while I get this settled, I'll be sure to >> post on that email thread. >> >> I'll send out a "it's really on" email once it is both on and working. >> >> It'll be running both the gtests (C++ unit tests) and the LLDB Python >> test suite. >> -- >> -Todd >> > > > > -- > -Todd > -- -Todd ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lists.llvm.org server maintenance, Friday Dec 18 @10:30 PST
The server maintenance is complete and lists should be operational. Thanks, Tanya > On Dec 17, 2015, at 12:06 PM, Tanya Lattner wrote: > > All, > > The server that runs the mailing lists will be down for maintenance starting > Friday Dec 18th at 10:30PM PST. I do not expect a long downtime, but please > keep this in mind if you see any issues with the lists during this period. I > will send an email once I am finished. > > No other services should be affected. > > Thanks, > Tanya ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
