[lldb-dev] [Bug 26206] New: TestExitDuringStep sometimes hangs on android
https://llvm.org/bugs/show_bug.cgi?id=26206 Bug ID: 26206 Summary: TestExitDuringStep sometimes hangs on android Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: lab...@google.com CC: llvm-b...@lists.llvm.org Classification: Unclassified Test sometimes hangs on the linux->android buildbot. The logs seem to indicate that the process is simply not hitting the breakpoint after the initial "run" command. It's hard to diagnose further without getting logs from the server (which we are not collecting at the moment). -- 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] Get source-map from python API?
If you mean "Add an API that sets the source-map for a target" say to SBTarget, then that sounds great. But if we're going to add an API to get at settings in general, then we should talk about it more broadly before anybody gets started. There was a bunch of stuff that we wanted to do with settings that we never got around to, but still want to do. In particular, we had intended some as yet unspecified syntax for restricting settings to particular scenarios. Not this, but something like: settings set target[OS=OSX].expr-prefix my_osx_prefix.h gives you an idea of what we had in mind. I'd rather not add a full on API for the settings till we decide either how we want to do this (which I think would be worth the effort but I don't think any of us have got time to address this right now) or to scrap it and go with flat settings. Jim > On Jan 15, 2016, at 11:28 AM, Greg Clayton wrote: > > That being said, feel free to add something the SB API and propose a patch. > > Greg > >> On Jan 14, 2016, at 3:13 PM, Jim Ingham via lldb-dev >> wrote: >> >> There is currently no API to access the settings. You have to cons up >> commands and use SBCommandInterpreter::HandleCommand to execute them. >> >> This is one of the remaining holes in the SB API. >> >> Jim >> >>> On Jan 14, 2016, at 2:41 PM, Jeffrey Tan via lldb-dev >>> wrote: >>> >>> Hi, >>> >>> We are building an IDE debugger on top of lldb python API. In order to get >>> the source remapping work(the source path embedded in the symbol may be >>> different from the real source path), user needs to use "settings set >>> target.source-map" command to remap the source. >>> >>> I would like users to do similar thing from our IDE debugger. However, I >>> could not find a python API to specify the source remapping, and more >>> important a way to access the remapping functionality. The SBSourceManager >>> class only exposes a single DisplaySourceLinesWithLineNumbers() method >>> which displays the source in console output. Ideally it should expose an >>> API in SBSourceManager for us to provide the old FileSpec and get back a >>> new remapped FileSpec. >>> >>> Is this not exposed in Python API? Do I need to re-do the remapping logic >>> in our IDE UI code? How is other IDE handling the source remapping? >>> >>> Thanks >>> Jeffrey >>> >>> ___ >>> 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 mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] Spurious process state change events
> On Jan 15, 2016, at 1:49 PM, Vadim Chugunov via lldb-dev > wrote: > > +lldb-dev > > On Fri, Jan 15, 2016 at 1:47 PM, Vadim Chugunov wrote: > Thanks, that was it! > > On Fri, Jan 15, 2016 at 1:00 PM, Pavel Labath wrote: > Hi, > > The stopped event should have the "restarted" flag set. You can use > the GetRestartedFromEvent function to check for that. (Let me know if > they don't). I think you can get this (under varying circumstances) on > other platforms as well, so you need to handle this everywhere. > > Somebody correct me if I'm wrong, but I believe that every restarted > should be then followed by a running event. No, if you get a stop event with the restarted bit set, the next event will be another stop event. It just seemed annoying, if you already know the process restarted, to have to turn around and wait for the running event. Jim > > cheers, > pl > > > On 15 January 2016 at 19:35, Vadim Chugunov via lldb-dev > wrote: > > Hi, > > I have a Python script that drives LLDB (in async mode), with a > > listener attached to the process. > > On OSX, upon the launch, LLDB emits a eStateRunning process state > > event, and then eventually eStateStopped - when a breakpoint is hit. > > On Linux, however, the initial eStateRunning is immediately followed > > by eStateStopped and another eStateRunning, without any intervention > > on my part. This messes things up for me somewhat, because my script > > thinks that a breakpoint has been hit and tries examine state of the > > process. > > So I have 2 questions: > > - Is it supposed to happen? > > - What would be the best way to filter out these spurious stop events? > > if is_linux and is_first_stop_event: ... feels a bit hacky. > > > > thanks! > > ___ > > 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 mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] Get source-map from python API?
> On Jan 19, 2016, at 10:58 AM, Jim Ingham wrote: > > If you mean "Add an API that sets the source-map for a target" say to > SBTarget, then that sounds great. Indeed this is what I meant to say. Add an API to SBTarget that allows you to modify the source map. > > But if we're going to add an API to get at settings in general, then we > should talk about it more broadly before anybody gets started. There was a > bunch of stuff that we wanted to do with settings that we never got around > to, but still want to do. In particular, we had intended some as yet > unspecified syntax for restricting settings to particular scenarios. Not > this, but something like: > > settings set target[OS=OSX].expr-prefix my_osx_prefix.h > > gives you an idea of what we had in mind. I'd rather not add a full on API > for the settings till we decide either how we want to do this (which I think > would be worth the effort but I don't think any of us have got time to > address this right now) or to scrap it and go with flat settings. Settings setting should be exposed only as accessors on the objects themselves and not in a generic way that allows you to set settings via the API that takes the setting name. So in general I vote to always add accessors on the objects and avoid anyone playing with settings by name and/or string values. > > Jim > > >> On Jan 15, 2016, at 11:28 AM, Greg Clayton wrote: >> >> That being said, feel free to add something the SB API and propose a patch. >> >> Greg >> >>> On Jan 14, 2016, at 3:13 PM, Jim Ingham via lldb-dev >>> wrote: >>> >>> There is currently no API to access the settings. You have to cons up >>> commands and use SBCommandInterpreter::HandleCommand to execute them. >>> >>> This is one of the remaining holes in the SB API. >>> >>> Jim >>> On Jan 14, 2016, at 2:41 PM, Jeffrey Tan via lldb-dev wrote: Hi, We are building an IDE debugger on top of lldb python API. In order to get the source remapping work(the source path embedded in the symbol may be different from the real source path), user needs to use "settings set target.source-map" command to remap the source. I would like users to do similar thing from our IDE debugger. However, I could not find a python API to specify the source remapping, and more important a way to access the remapping functionality. The SBSourceManager class only exposes a single DisplaySourceLinesWithLineNumbers() method which displays the source in console output. Ideally it should expose an API in SBSourceManager for us to provide the old FileSpec and get back a new remapped FileSpec. Is this not exposed in Python API? Do I need to re-do the remapping logic in our IDE UI code? How is other IDE handling the source remapping? Thanks Jeffrey ___ 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 mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [3.8 Release] RC1 has been tagged
Dear testers, Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at r258223. (It took a little longer than I'd planned, sorry about that.) There are still a bunch of open merge requests and bug reports, but I wanted to get the tag in so we can see what the build and test status are on the various platforms. I verified that it currently builds and tests cleanly for me on x86_64 Linux, Mac OS X* and Windows. Please build, test, and upload binaries to the sftp. Let me know if how it goes. Thanks, Hans [*] For Mac, I had to set CFLAGS="-isysroot `xcrun -show-sdk-path`" CXXFLAGS="-isysroot `xcrun -show-sdk-path`" for the build to work, otherwise stage-2 Clang couldn't find the SDK. I don't remember if I had to do this last time; maybe some upgrade changed something. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [3.8 Release] RC1 has been tagged
(cc'ing non-legacy llvm-dev this time; apologies if you get this twice. Please don't reply-all to the first one.) On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg wrote: > Dear testers, > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at > r258223. (It took a little longer than I'd planned, sorry about that.) > > There are still a bunch of open merge requests and bug reports, but I > wanted to get the tag in so we can see what the build and test status > are on the various platforms. > > I verified that it currently builds and tests cleanly for me on x86_64 > Linux, Mac OS X* and Windows. > > Please build, test, and upload binaries to the sftp. Let me know if how it > goes. > > Thanks, > Hans > > > [*] For Mac, I had to set CFLAGS="-isysroot `xcrun -show-sdk-path`" > CXXFLAGS="-isysroot `xcrun -show-sdk-path`" for the build to work, > otherwise stage-2 Clang couldn't find the SDK. I don't remember if I > had to do this last time; maybe some upgrade changed something. ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
