search for: jmorse

...abstractions summary of how the program behaved. [0] https://reviews.llvm.org/D54187#1290282 [1] https://github.com/SNSystems/dexter [2] https://www.youtube.com/watch?v=XRT_GmpGjXE [3] https://llvm.org/devmtg/2018-04/slides/Bedwell-Measuring_the_User_Debugging_Experience.pdf [4] https://github.com/jmorse/dexter/tree/f46f13f778484ed5c6f7bf33b8fc2d4837ff7265/tests/nostdlib/llvm_passes [5] https://github.com/llvm/llvm-project/tree/master/debuginfo-tests -- Thanks, Jeremy

...some non-X86 backends (certain TargetInstrInfo hooks need to perform debug-info bookkeeping), which would make this all more appetising. [0] http://lists.llvm.org/pipermail/llvm-dev/2020-February/139440.html [1] http://lists.llvm.org/pipermail/llvm-dev/2020-June/142368.html [2] https://github.com/jmorse/llvm-inst-ref-test-samples [3] https://reviews.llvm.org/D86813 [4] https://reviews.llvm.org/D88898 [5] https://github.com/jmorse/llvm-project/commit/0a702b967927d888bd222806252783359fc74d57 -- Thanks, Jeremy

+ 1 to Paul’s suggestions. I’d add that if an open bug report isn’t assigned to anyone, you can assume it’s fair game. Feel free to assign a bug to yourself if you start working on it. To toss another idea out there, you might try picking a small .o and working backwards to figure out why location information in it is incorrect. This can reveal a different set of bugs compared to e.g. running

...or register location). Wheras in the coroutine code you're generating the variable address doesn't get storage. If [0] is useful for you I can get that landed; it'd be good to hear whether this resolves the dbg.addr intrinsics not having an affect on the output. [0] https://github.com/jmorse/llvm-project/commit/40927e6c2b71ec914d937287a0c2ca6c52c01f6b -- Thanks, Jeremy

...in > TargetInstrInfo hooks need to perform debug-info bookkeeping), which would make > this all more appetising. > > [0] http://lists.llvm.org/pipermail/llvm-dev/2020-February/139440.html > [1] http://lists.llvm.org/pipermail/llvm-dev/2020-June/142368.html > [2] https://github.com/jmorse/llvm-inst-ref-test-samples > [3] https://reviews.llvm.org/D86813 > [4] https://reviews.llvm.org/D88898 > [5] https://github.com/jmorse/llvm-project/commit/0a702b967927d888bd222806252783359fc74d57 > > -- > Thanks, > Jeremy

...: this path can lead, slowly, to there being no debug instructions for variable locations! And as described in my RFC sitrep-email, it can be more accurate than location only tracking too. [0] http://lists.llvm.org/pipermail/llvm-dev/2020-February/139440.html [1] Branch is here: https://github.com/jmorse/llvm-project/commits/ldvars-separation , tip is 11450def5bc592321ece2a64ea2a8cabbc614c39 at time of sending. I could open a PR containing the changes, but github mucks them up; best to just look at the bare file [8]. [2] http://lists.llvm.org/pipermail/llvm-dev/2020-February/139469.html [3] https:/...

...u're generating the variable address doesn't get storage. >> >> If [0] is useful for you I can get that landed; it'd be good to hear >> whether this resolves the dbg.addr intrinsics not having an affect on >> the output. >> >> [0] https://github.com/jmorse/llvm-project/commit/40927e6c2b71ec914d937287a0c2ca6c52c01f6b >> >> -- >> Thanks, >> Jeremy > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -...

...described are here [1]. We're also working on some sequencing commands ("this state is seen before that state") to better test optimized debuginfo. Proposal ------------ Our patch is up here: https://reviews.llvm.org/D68708 You can browse the tree on github here: https://github.com/jmorse/llvm-project/tree/dexter-rfc It imports Dexter into the debuginfo-tests repository, and converts many existing debuginfo-tests to run with Dexter. We'd suggest that future debuginfo integration tests use Dexter to run by default, so that we can build a testsuite ensuring clang/llvms debuginfo...

...9;re generating the variable address doesn't get storage. > > > > If [0] is useful for you I can get that landed; it'd be good to hear > > whether this resolves the dbg.addr intrinsics not having an affect on > > the output. > > > > [0] https://github.com/jmorse/llvm-project/commit/40927e6c2b71ec914d937287a0c2ca6c52c01f6b > > > > -- > > Thanks, > > Jeremy > > > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org > > https://lists.llvm.org/cgi...

Apologies for the slow response here Jeremy. Your reply has been incredibly helpful so far, I just need to try adding 'llvm.dbg.addr' myself to confirm that works. Thank you! - Brian Gesiak On Thu, Feb 6, 2020 at 11:04 AM Jeremy Morse <jeremy.morse.llvm at gmail.com> wrote: > Hi Brian, > > Thanks for working on coroutines, the debugging experience, and in > particular

...s:x:id:user1,user2 How can ntusers group be seen on a w2k workstation that is a member of a Samba controlled domain? Thanx Dax __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ Return-Path: <jmorse@lsil.com> Delivered-To: samba@lists.samba.org Received: from mail2.lsil.com (mail2.lsil.com [147.145.40.22]) by lists.samba.org (Postfix) with ESMTP id 41BE9443E for <samba@lists.samba.org>; Tue, 29 May 2001 10:29:27 -0700 (PDT) Received: from mhbs.lsil.com (mhbs [147.145.31.100]) by m...

...amba.org/pipermail/samba/ On Thu, 24 May 2001 bblack@allstor-sw.co.uk wrote: > > Not sure, the figures below are the ones quoted in the samba manual I > think. This has been a source of confusion is all our documentation (and books) for a long time. Cheers, jerry Return-Path: <jmorse@lsil.com> Delivered-To: samba@lists.samba.org Received: from mail2.lsil.com (mail2.lsil.com [147.145.40.22]) by lists.samba.org (Postfix) with ESMTP id 861865329 for <samba@lists.samba.org>; Thu, 24 May 2001 09:22:39 -0700 (PDT) Received: from mhbs.lsil.com (mhbs [147.145.31.100]) by m...