Re: [lldb-dev] [llvm-dev] Renaming The Default Branch
Hi, On Sun, 6 Dec 2020, Mike Edwards via llvm-dev wrote: The change to the default branch setting has been completed. The new default branch for the llvm-project is now 'main'. Pushes to the 'master' branch will no longer be accepted. Please update your workflow to use the new 'main' branch. Thank you for your patience and cooperation during this process. I hope everyone has a nice, productive day. I just pushed a patch to the new main branch, and I've noticed these issues: - The master branch isn't updated to reflect this. Afaik it was supposed that the master branch, while read only, would still receive updates until it's being discontinued - or did I misunderstand that bit? - Phabricator doesn't seem to pick up on commits to master, and doesn't autoclose reviews based on pushed patches. I guess this would be fixed by either making it track the main branch, or if new commits are mirrored into the previous branch until Phabricator is switched? // Martin ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [llvm-dev] Renaming The Default Branch
Hi Martin, It seems it's in the `master` branch: https://github.com/llvm/llvm-project/commit/78a57069b53a08d5aef98a8472fcfa73dbbc8771 So, is the problem resolved? On Mon, Dec 7, 2020 at 11:12 AM Martin Storsjö via cfe-dev wrote: > > Hi, > > On Sun, 6 Dec 2020, Mike Edwards via llvm-dev wrote: > > > The change to the default branch setting has been completed. The new > > default branch for the llvm-project is now 'main'. Pushes to the 'master' > > branch will no longer be accepted. Please update your workflow to use the > > new 'main' branch. Thank you for your patience and cooperation during this > > process. I hope everyone has a nice, productive day. > > I just pushed a patch to the new main branch, and I've noticed these > issues: > > - The master branch isn't updated to reflect this. Afaik it was supposed > that the master branch, while read only, would still receive updates until > it's being discontinued - or did I misunderstand that bit? > > - Phabricator doesn't seem to pick up on commits to master, and doesn't > autoclose reviews based on pushed patches. I guess this would be fixed by > either making it track the main branch, or if new commits are mirrored > into the previous branch until Phabricator is switched? > > // Martin > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev -- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [llvm-dev] Renaming The Default Branch
Hi Anton, On Mon, 7 Dec 2020, Anton Korobeynikov wrote: It seems it's in the `master` branch: https://github.com/llvm/llvm-project/commit/78a57069b53a08d5aef98a8472fcfa73dbbc8771 So, is the problem resolved? Yes, now the branch seems to have updated - I guess I didn't wait for long enough if that happens asynchronously. The associated review hasn't been autoclosed yet though, but maybe I should give that some more time as well. // Martin ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 18522] TestThreadSpecificBreakpoint test fails on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=18522 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||mgo...@gentoo.org -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 19246] TestCallThatRestarts test fails intermittently
https://bugs.llvm.org/show_bug.cgi?id=19246 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||mgo...@gentoo.org --- Comment #7 from Michał Górny --- Yeah, I don't recall it even being flaky for me, so let's close it as FIXED. We can always reopen if it happens again. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 19605] FreeBSD buildbot TestCallWithTimeout failure after r206835
https://bugs.llvm.org/show_bug.cgi?id=19605 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from Michał Górny --- I can't reproduce right now and I don't recall it ever failing for me. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 20545] PythonSynthDataFormatterTestCase.test_with_dwarf_and_run_command has all 'expect' output on stdout/test log
https://bugs.llvm.org/show_bug.cgi?id=20545 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 20548] 5 DataFormatter tests fail to build on the lab.llvm.org FreeBSD buildbot as libstdc++ is not included in FreeBSD 10.0
https://bugs.llvm.org/show_bug.cgi?id=20548 Michał Górny changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||mgo...@gentoo.org --- Comment #4 from Michał Górny --- Unless I'm mistaken, all the tests are decorated properly today. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 20549] SingleQuoteInCommandLineTestCase, CommandRegexTestCase, CommandLineCompletionTestCase time out on lab.llvm.org FreeBSD buildbot
https://bugs.llvm.org/show_bug.cgi?id=20549 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||mgo...@gentoo.org --- Comment #2 from Michał Górny --- I'm going to close it since I didn't ever see it myself. We can reopen if someone else sees it. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 20550] StaticVariableTestCase fails on lab.llvm.org FreeBSD buildbot
https://bugs.llvm.org/show_bug.cgi?id=20550 Michał Górny changed: What|Removed |Added Status|NEW |RESOLVED CC||mgo...@gentoo.org Resolution|--- |FIXED --- Comment #2 from Michał Górny --- Passes for me today, and I didn't ever see it fail. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 21375] test_with_dwarf (TestCPPBreakpoints.CPPBreakpointTestCase) failing (-F only finds ::Function)
https://bugs.llvm.org/show_bug.cgi?id=21375 Michał Górny changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||mgo...@gentoo.org --- Comment #1 from Michał Górny --- It's test/API/lang/cpp/exceptions/TestCPPExceptionBreakpoints.py today. It passes for me today, and I don't recall seeing it fail. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 23318] SendSignalTestCase.test_with_dwarf_and_run_command fails on FreeBSD with "False is not True : It was the running state"
https://bugs.llvm.org/show_bug.cgi?id=23318 Michał Górny changed: What|Removed |Added Status|NEW |RESOLVED CC||mgo...@gentoo.org Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 24896] "Process 1 was reported... but no stop reply packet was received" error from TestConnectRemote on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=24896 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Michał Górny --- This test works now that we have a remote plugin. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25057] On x86_64-FreeBSD Platform, LLDB hangs while debugging an inferior with 'int3' assembly instruction.
https://bugs.llvm.org/show_bug.cgi?id=25057 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25624] TestFdLeak fails on FreeBSD with Python 2.7.10
https://bugs.llvm.org/show_bug.cgi?id=25624 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #6 from Michał Górny --- This test should be good now. Besides, LLDB no longer supports Python 2. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25625] TestCppIncompleteTypes failing on FreeBSD 11 buildbot
https://bugs.llvm.org/show_bug.cgi?id=25625 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #1 from Michał Górny --- The test passes for me now. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 25626] expectedFailureClang decorator may not work on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=25626 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Michał Górny --- The decorator seems to work fine now, so I've removed the duplicate xfail for FreeBSD. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 26565] test_expr_with_macros_dwarf (TestMacros.TestMacros) failing on FreeBSD 11
https://bugs.llvm.org/show_bug.cgi?id=26565 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #3 from Michał Górny --- It's marked xfail for clang, so I suppose there's nothing specific to be done for FreeBSD. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 26566] test_with_run_command_dwarf (TestDataFormatterLibcxxListLoop.LibcxxListDataFormatterTestCase) failing on FreeBS 11
https://bugs.llvm.org/show_bug.cgi?id=26566 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Michał Górny --- Works for me. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 26924] LLDB doesn't handle FreeBSD's setproctitle() call properly
https://bugs.llvm.org/show_bug.cgi?id=26924 Michał Górny changed: What|Removed |Added CC||mgo...@gentoo.org Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Michał Górny --- This is fixed with the new plugin. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 26937] TestRegisterVariables failing with Clang 3.4.1 on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=26937 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #2 from Michał Górny --- I see it's restricted to old clang today, and it passes for me on 13.0. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 36527] test_*int*_t_dwarf failing on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=36527 Michał Górny changed: What|Removed |Added Resolution|--- |FIXED CC||mgo...@gentoo.org Status|NEW |RESOLVED --- Comment #2 from Michał Górny --- The tests changed a bit and they certainly don't fail for me now. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] Renaming The Default Branch
Nice! One issue that I noticed is that it seems all commit emails now go to the llvm-branch-commits mailing list. For example, http://lists.llvm.org/pipermail/llvm-branch-commits/2020-December/015623.html was pushed to 'main', but still went to this list which is supposed to be for commits to release branches and such. Is there some way that can be fixed? Thanks, Hans On Mon, Dec 7, 2020 at 7:38 AM Mike Edwards via llvm-dev wrote: > > Hello, > The change to the default branch setting has been completed. The new default > branch for the llvm-project is now 'main'. Pushes to the 'master' branch > will no longer be accepted. Please update your workflow to use the new > 'main' branch. Thank you for your patience and cooperation during this > process. I hope everyone has a nice, productive day. > > Respectfully, > > Mike Edwards > On Behalf Of the LLVM Foundation > > On Sun, Dec 6, 2020 at 9:54 PM Mike Edwards wrote: >> >> Hello, >> This is a reminder the process to rename the default branch to main will >> begin in approximately 10 minutes. An update will be sent to the lists once >> the process has been completed and the branch is open to receive new commits. >> >> Thanks, >> Mike Edwards >> >> On Fri, Nov 13, 2020 at 3:56 PM Mike Edwards wrote: >>> >>> Hi Everyone, >>> Many tech communities, including GitHub and Git, have moved away from term >>> “master branch” and replaced it with “main branch” in an >>> effort to remove unnecessary references to slavery and use more inclusive >>> terms. This was also discussed on the LLVM-dev mailing list >>> and there was strong consensus from LLVM Developers’ that the LLVM Project >>> should also rename our master branch as well. Now that >>> an industry standard name has been selected by GitHub, the LLVM Project can >>> begin the renaming process of the default branch to “main”. >>> >>> This change will occur at **06:00GMT on Monday December 7, 2020** (time is >>> **GMT**, please adjust for your local timezone). >>> >>> To make this as easy as possible we plan to do the following prior to >>> November 20, 2020: >>> * Create a new branch named 'test-main' on the llvm-project repository >>> * This branch will be read-only except for the llvmbot account >>> * Setup a GitHub action to mirror commits from 'master' to ‘test-main' >>> automatically >>> * Allow the configuration to soak for a few days to ensure everything >>> works >>> * Create a new branch named “main” on the llvm-project repository >>> * This branch will be readonly initially >>> * Reuse the previous Github Action to mirror master to main >>> * This configuration will stay in place until cutover takes place on >>> Dec. 7 >>> >>> On December 7, 2020: >>> * We will lock the master branch and change it to be readonly (with the >>> exception of llvmbot) >>> * Switch the GitHub action to mirror commits from the new main branch back >>> to the old master branch >>> * Make a few test commits to ensure the GitHub action is functioning as >>> expected >>> * Open the main branch to commits from community members >>> * In parallel we will begin to work through the rest of the llvm >>> organization repositories to update branch names as well >>> * We will update the developer policy to reflect the change in workflow >>> >>> On January 7, 2021: >>> * We will remove the ‘master’ branch from all repositories in the llvm >>> organization >>> >>> As we work towards December 7, 2020 we are going to set up a test of this >>> system on a fork of the llvm-project >>> in order to simulate the cutover. If we encounter any issues we will update >>> the community on llvm-dev. >>> We expect the llvm-project repository to be unavailable to developers for >>> approximately 1 hour while the >>> switch is made. Lockout will occur promptly at 06:00GMT on the 7th. >>> Certainly if we finish sooner, we will >>> update llvm-dev to let everyone know the repository is available for use >>> once again. >>> >>> We know this has been a long process and we want to thank everyone for >>> their patience. We look forward to getting >>> the project completed soon. >>> >>> Respectfully, >>> >>> Mike Edwards >>> On Behalf Of the LLVM Foundation > > ___ > LLVM Developers mailing list > llvm-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] Renaming The Default Branch
Hi, Currently there are two issues I would like to address: 1) While we understand new commits to the 'main' branch are somewhat slow to synchronize (about 5 minutes) to the old 'master' branch, we are not planning to address the issue at this time. Developers will notice an immediate improvement by migrating their workflows to the new 'main' branch. We advise everyone to stop relying on 'master' and migrate to the 'main' branch as soon as possible. 2) As Hans just pointed out, the automation we have in place to make commits post to the mailing lists is not working correctly. I will be looking into this today and hope to have it resolved soon. -Mike On Mon, Dec 7, 2020 at 6:35 AM Hans Wennborg wrote: > Nice! > > One issue that I noticed is that it seems all commit emails now go to > the llvm-branch-commits mailing list. For example, > > http://lists.llvm.org/pipermail/llvm-branch-commits/2020-December/015623.html > was pushed to 'main', but still went to this list which is supposed to > be for commits to release branches and such. > > Is there some way that can be fixed? > > Thanks, > Hans > > On Mon, Dec 7, 2020 at 7:38 AM Mike Edwards via llvm-dev > wrote: > > > > Hello, > > The change to the default branch setting has been completed. The new > default branch for the llvm-project is now 'main'. Pushes to the 'master' > branch will no longer be accepted. Please update your workflow to use the > new 'main' branch. Thank you for your patience and cooperation during this > process. I hope everyone has a nice, productive day. > > > > Respectfully, > > > > Mike Edwards > > On Behalf Of the LLVM Foundation > > > > On Sun, Dec 6, 2020 at 9:54 PM Mike Edwards wrote: > >> > >> Hello, > >> This is a reminder the process to rename the default branch to main > will begin in approximately 10 minutes. An update will be sent to the > lists once the process has been completed and the branch is open to receive > new commits. > >> > >> Thanks, > >> Mike Edwards > >> > >> On Fri, Nov 13, 2020 at 3:56 PM Mike Edwards wrote: > >>> > >>> Hi Everyone, > >>> Many tech communities, including GitHub and Git, have moved away from > term “master branch” and replaced it with “main branch” in an > >>> effort to remove unnecessary references to slavery and use more > inclusive terms. This was also discussed on the LLVM-dev mailing list > >>> and there was strong consensus from LLVM Developers’ that the LLVM > Project should also rename our master branch as well. Now that > >>> an industry standard name has been selected by GitHub, the LLVM > Project can begin the renaming process of the default branch to “main”. > >>> > >>> This change will occur at **06:00GMT on Monday December 7, 2020** > (time is **GMT**, please adjust for your local timezone). > >>> > >>> To make this as easy as possible we plan to do the following prior to > November 20, 2020: > >>> * Create a new branch named 'test-main' on the llvm-project repository > >>> * This branch will be read-only except for the llvmbot account > >>> * Setup a GitHub action to mirror commits from 'master' to > ‘test-main' automatically > >>> * Allow the configuration to soak for a few days to ensure > everything works > >>> * Create a new branch named “main” on the llvm-project repository > >>> * This branch will be readonly initially > >>> * Reuse the previous Github Action to mirror master to main > >>> * This configuration will stay in place until cutover takes place > on Dec. 7 > >>> > >>> On December 7, 2020: > >>> * We will lock the master branch and change it to be readonly (with > the exception of llvmbot) > >>> * Switch the GitHub action to mirror commits from the new main branch > back to the old master branch > >>> * Make a few test commits to ensure the GitHub action is functioning > as expected > >>> * Open the main branch to commits from community members > >>> * In parallel we will begin to work through the rest of the llvm > organization repositories to update branch names as well > >>> * We will update the developer policy to reflect the change in workflow > >>> > >>> On January 7, 2021: > >>> * We will remove the ‘master’ branch from all repositories in the llvm > organization > >>> > >>> As we work towards December 7, 2020 we are going to set up a test of > this system on a fork of the llvm-project > >>> in order to simulate the cutover. If we encounter any issues we will > update the community on llvm-dev. > >>> We expect the llvm-project repository to be unavailable to developers > for approximately 1 hour while the > >>> switch is made. Lockout will occur promptly at 06:00GMT on the 7th. > Certainly if we finish sooner, we will > >>> update llvm-dev to let everyone know the repository is available for > use once again. > >>> > >>> We know this has been a long process and we want to thank everyone for > their patience. We look forward to getting > >>> the project completed soon. > >>> > >>> Respectfully, > >>> > >>> Mike Edw
[lldb-dev] [Bug 48433] New: Crash on "help memory read"
https://bugs.llvm.org/show_bug.cgi?id=48433 Bug ID: 48433 Summary: Crash on "help memory read" Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: kparz...@quicinc.com CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org The command "help memory read" causes a crash. No other action is required, load lldb and ask for help about "memory read". $ lldb (lldb) help memory read PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace. Stack dump: 0. Program arguments: /w/c/org/bin/lldb #0 0x0042cdc3 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/w/c/org/bin/lldb+0x42cdc3) #1 0x0042b07e llvm::sys::RunSignalHandlers() (/w/c/org/bin/lldb+0x42b07e) #2 0x0042d405 SignalHandler(int) (/w/c/org/bin/lldb+0x42d405) #3 0x7f78efde6890 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12890) #4 0x7f78e8980c70 lldb_private::Options::GenerateOptionUsage(lldb_private::Stream&, lldb_private::CommandObject*, unsigned int) (/w/c/org/bin/../lib/liblldb.so.12git+0x1000c70) #5 0x7f78e896d8eb lldb_private::CommandObject::GenerateHelpText(lldb_private::Stream&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfed8eb) #6 0x7f78e896d75e lldb_private::CommandObject::GenerateHelpText(lldb_private::CommandReturnObject&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfed75e) #7 0x7f78ea2ac4be lldb_private::CommandObjectHelp::DoExecute(lldb_private::Args&, lldb_private::CommandReturnObject&) (/w/c/org/bin/../lib/liblldb.so.12git+0x292c4be) #8 0x7f78e896e02c lldb_private::CommandObjectParsed::Execute(char const*, lldb_private::CommandReturnObject&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfee02c) #9 0x7f78e8964b4c lldb_private::CommandInterpreter::HandleCommand(char const*, lldb_private::LazyBool, lldb_private::CommandReturnObject&, lldb_private::ExecutionContext*, bool, bool) (/w/c/org/bin/../lib/liblldb.so.12git+0xfe4b4c) #10 0x7f78e8968253 lldb_private::CommandInterpreter::IOHandlerInputComplete(lldb_private::IOHandler&, std::__1::basic_string, std::__1::allocator >&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfe8253) #11 0x7f78e88d2d9d lldb_private::IOHandlerEditline::Run() (/w/c/org/bin/../lib/liblldb.so.12git+0xf52d9d) #12 0x7f78e88b932d lldb_private::Debugger::RunIOHandlers() (/w/c/org/bin/../lib/liblldb.so.12git+0xf3932d) #13 0x7f78e89695eb lldb_private::CommandInterpreter::RunCommandInterpreter(lldb_private::CommandInterpreterRunOptions&) (/w/c/org/bin/../lib/liblldb.so.12git+0xfe95eb) #14 0x7f78e85bcd49 lldb::SBDebugger::RunCommandInterpreter(bool, bool) (/w/c/org/bin/../lib/liblldb.so.12git+0xc3cd49) #15 0x00409fb6 Driver::MainLoop() (/w/c/org/bin/lldb+0x409fb6) #16 0x0040c215 main (/w/c/org/bin/lldb+0x40c215) #17 0x7f78e62a3b97 __libc_start_main /build/glibc-OTsEL5/glibc-2.27/csu/../csu/libc-start.c:344:0 #18 0x00406cca _start (/w/c/org/bin/lldb+0x406cca) Segmentation fault -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [llvm-dev] Renaming The Default Branch
On Mon, Dec 7, 2020 at 4:38 PM Hubert Tong wrote: > On Mon, Dec 7, 2020 at 10:59 AM Mike Edwards via cfe-dev < > cfe-...@lists.llvm.org> wrote: > >> Hi, >> Currently there are two issues I would like to address: >> >> 1) While we understand new commits to the 'main' branch are somewhat slow >> to synchronize (about 5 minutes) to the old 'master' branch, we are not >> planning to address the issue at this time. Developers will notice an >> immediate improvement by migrating their workflows to the new 'main' >> branch. We advise everyone to stop relying on 'master' and migrate to the >> 'main' branch as soon as possible. >> > When will it be correct to push to `main` for all of the repos under the > GitHub org? > Hi Hubert, I do not have a specific timeline defined as of yet. My hope is to get all of the other projects under the llvm org migrated to using a 'main' branch by default prior to the end of January 2021. I do not control all of the other repositories though, so I will be working with their owners to accomplish this according to a schedule which will cause the least disruption to the individual projects. Thanks, Mike > > >> >> 2) As Hans just pointed out, the automation we have in place to make >> commits post to the mailing lists is not working correctly. I will be >> looking into this today and hope to have it resolved soon. >> >> -Mike >> >> On Mon, Dec 7, 2020 at 6:35 AM Hans Wennborg wrote: >> >>> Nice! >>> >>> One issue that I noticed is that it seems all commit emails now go to >>> the llvm-branch-commits mailing list. For example, >>> >>> http://lists.llvm.org/pipermail/llvm-branch-commits/2020-December/015623.html >>> was pushed to 'main', but still went to this list which is supposed to >>> be for commits to release branches and such. >>> >>> Is there some way that can be fixed? >>> >>> Thanks, >>> Hans >>> >>> On Mon, Dec 7, 2020 at 7:38 AM Mike Edwards via llvm-dev >>> wrote: >>> > >>> > Hello, >>> > The change to the default branch setting has been completed. The new >>> default branch for the llvm-project is now 'main'. Pushes to the 'master' >>> branch will no longer be accepted. Please update your workflow to use the >>> new 'main' branch. Thank you for your patience and cooperation during this >>> process. I hope everyone has a nice, productive day. >>> > >>> > Respectfully, >>> > >>> > Mike Edwards >>> > On Behalf Of the LLVM Foundation >>> > >>> > On Sun, Dec 6, 2020 at 9:54 PM Mike Edwards wrote: >>> >> >>> >> Hello, >>> >> This is a reminder the process to rename the default branch to main >>> will begin in approximately 10 minutes. An update will be sent to the >>> lists once the process has been completed and the branch is open to receive >>> new commits. >>> >> >>> >> Thanks, >>> >> Mike Edwards >>> >> >>> >> On Fri, Nov 13, 2020 at 3:56 PM Mike Edwards wrote: >>> >>> >>> >>> Hi Everyone, >>> >>> Many tech communities, including GitHub and Git, have moved away >>> from term “master branch” and replaced it with “main branch” in an >>> >>> effort to remove unnecessary references to slavery and use more >>> inclusive terms. This was also discussed on the LLVM-dev mailing list >>> >>> and there was strong consensus from LLVM Developers’ that the LLVM >>> Project should also rename our master branch as well. Now that >>> >>> an industry standard name has been selected by GitHub, the LLVM >>> Project can begin the renaming process of the default branch to “main”. >>> >>> >>> >>> This change will occur at **06:00GMT on Monday December 7, 2020** >>> (time is **GMT**, please adjust for your local timezone). >>> >>> >>> >>> To make this as easy as possible we plan to do the following prior >>> to November 20, 2020: >>> >>> * Create a new branch named 'test-main' on the llvm-project >>> repository >>> >>> * This branch will be read-only except for the llvmbot account >>> >>> * Setup a GitHub action to mirror commits from 'master' to >>> ‘test-main' automatically >>> >>> * Allow the configuration to soak for a few days to ensure >>> everything works >>> >>> * Create a new branch named “main” on the llvm-project repository >>> >>> * This branch will be readonly initially >>> >>> * Reuse the previous Github Action to mirror master to main >>> >>> * This configuration will stay in place until cutover takes >>> place on Dec. 7 >>> >>> >>> >>> On December 7, 2020: >>> >>> * We will lock the master branch and change it to be readonly (with >>> the exception of llvmbot) >>> >>> * Switch the GitHub action to mirror commits from the new main >>> branch back to the old master branch >>> >>> * Make a few test commits to ensure the GitHub action is functioning >>> as expected >>> >>> * Open the main branch to commits from community members >>> >>> * In parallel we will begin to work through the rest of the llvm >>> organization repositories to update branch names as well >>> >>> * We will update the developer policy to reflect the change in >>> workflow
