[lldb-dev] LLDB for bare-iron targets lacking support for qC /qfThreadInfo packet
Hi, The gdb-stub running on a MIPS bare-iron board lacks support for qC /qfThreadInfo packet. Once the LLDB is connected to the target it cannot proceed further as there is no process and/or thread information available from the target. However GDB is able to debug the application as it ignores the output of qC /qfThreadInfo packet if they are not supported. GDB assumes that a process/thread X is available for debugging. Is there any way in LLDB to support such bare-iron targets where qC /qfThreadInfo packets are not supported? Regards, Jaydeep ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [3.7 Release] RC3 has been tagged, let's wrap this up
Hm, it does not seem to compile at all here? The build ends with: In file included from /home/dim/llvm-3.7.0/rc3/llvm.src/tools/clang/tools/extra/clang-apply-replacements/lib/Tooling/ApplyReplacements.cpp:17: /home/dim/llvm-3.7.0/rc3/llvm.src/tools/clang/tools/extra/clang-apply-replacements/lib/Tooling/../../include/clang-apply-replacements/Tooling/ApplyReplacements.h:19:10: fatal error: 'clang/Tooling/Refactoring.h' file not found #include "clang/Tooling/Refactoring.h" ^ 1 error generated. Any idea? I had no problems at all with -rc2. -Dimitry > On 21 Aug 2015, at 02:51, Hans Wennborg wrote: > > Hello everyone, > > 3.7-rc3 has just been tagged. Testers, please test, build binaries, > upload to the sftp and report results to this thread. > > Again, a lot of patches got merged between rc2 and rc3, but hopefully > nothing that should upset things. > > One thing that did change is that the release script now correctly > symlinks clang-tools-extra into the build. If this causes problems on > your platform, please just remove it. > > This is a release candidate in the real sense: at this point I have > zero release blockers on my radar. I will now only accept fixes for > critical regressions, and if nothing comes up, rc3 will be promoted to > 3.7.0-final. > > Documentation and release note patches are still welcome all the way > up until the final tag goes in. > > Issues that were on my radar, but I don't consider blocking: > > - Sanitizer test failures on various platforms, e.g. PR24222. We never > ran these tests in previous releases, so it's not a regression. It > would be great if the sanitizer folks could look into the test > failures, but it's not blocking 3.7. > > - PR24273: "[ARM] Libc++abi built in-tree with libunwind fails in > __cxa_allocate_exception", Renato will exclude libc++ from his build > for now. > > - Lack of key functions in some Instruction classes causing build > failures without -fno-rtti > (http://lists.llvm.org/pipermail/llvm-dev/2015-August/089010.html). No > patches have been forthcoming, so this will not get fixed for 3.7. At > least we correctly report -fno-rtti in llvm-config built with CMake > now. > > - r244221: "[SPARC] Don't compare arch name as a string, use the enum > instead", owner is unresponsive. > > - "[lldb] r245020 - [MIPS]Handle floating point and aggregate return > types in SysV-mips [32 bit] ABI", owner is unresponsive. > > > Cheers, > Hans signature.asc Description: Message signed with OpenPGP using GPGMail ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 24530] New: LLDB can miss inferior SIGSTOP and SIGINT under some circumstances
https://llvm.org/bugs/show_bug.cgi?id=24530 Bug ID: 24530 Summary: LLDB can miss inferior SIGSTOP and SIGINT under some circumstances Product: lldb Version: unspecified Hardware: PC OS: All 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 This happens when the inferior gets a signal at the same time we are trying to interrupt it. If the signal is SIGSTOP or SIGINT, the interrupt machinery in GDBRemoteCommunicationClient::SendContinuePacketAndWaitForResponse can mistake the real signal stop for the maintenance stop and resume the process incorrectly. RaiseTestCase.restart_bug_test reproduces this behavior. The bug affect all targets which use the remote stub. -- 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] [3.7 Release] RC3 has been tagged, let's wrap this up
Hi Dmitry, if I understood Hans clang-extra wasn't part of the build prior to rc3. Just delete it and run script with --no-checkout. On Fri, Aug 21, 2015 at 7:15 PM, Dimitry Andric wrote: > Hm, it does not seem to compile at all here? The build ends with: > > In file included from > /home/dim/llvm-3.7.0/rc3/llvm.src/tools/clang/tools/extra/clang-apply-replacements/lib/Tooling/ApplyReplacements.cpp:17: > /home/dim/llvm-3.7.0/rc3/llvm.src/tools/clang/tools/extra/clang-apply-replacements/lib/Tooling/../../include/clang-apply-replacements/Tooling/ApplyReplacements.h:19:10: > fatal error: 'clang/Tooling/Refactoring.h' file not found > #include "clang/Tooling/Refactoring.h" > ^ > 1 error generated. > > Any idea? I had no problems at all with -rc2. > > -Dimitry > > > On 21 Aug 2015, at 02:51, Hans Wennborg wrote: > > > > Hello everyone, > > > > 3.7-rc3 has just been tagged. Testers, please test, build binaries, > > upload to the sftp and report results to this thread. > > > > Again, a lot of patches got merged between rc2 and rc3, but hopefully > > nothing that should upset things. > > > > One thing that did change is that the release script now correctly > > symlinks clang-tools-extra into the build. If this causes problems on > > your platform, please just remove it. > > > > This is a release candidate in the real sense: at this point I have > > zero release blockers on my radar. I will now only accept fixes for > > critical regressions, and if nothing comes up, rc3 will be promoted to > > 3.7.0-final. > > > > Documentation and release note patches are still welcome all the way > > up until the final tag goes in. > > > > Issues that were on my radar, but I don't consider blocking: > > > > - Sanitizer test failures on various platforms, e.g. PR24222. We never > > ran these tests in previous releases, so it's not a regression. It > > would be great if the sanitizer folks could look into the test > > failures, but it's not blocking 3.7. > > > > - PR24273: "[ARM] Libc++abi built in-tree with libunwind fails in > > __cxa_allocate_exception", Renato will exclude libc++ from his build > > for now. > > > > - Lack of key functions in some Instruction classes causing build > > failures without -fno-rtti > > (http://lists.llvm.org/pipermail/llvm-dev/2015-August/089010.html). No > > patches have been forthcoming, so this will not get fixed for 3.7. At > > least we correctly report -fno-rtti in llvm-config built with CMake > > now. > > > > - r244221: "[SPARC] Don't compare arch name as a string, use the enum > > instead", owner is unresponsive. > > > > - "[lldb] r245020 - [MIPS]Handle floating point and aggregate return > > types in SysV-mips [32 bit] ABI", owner is unresponsive. > > > > > > Cheers, > > Hans > > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [3.7 Release] RC3 has been tagged, let's wrap this up
Strangely, the clang-tools-extra stuff does build if I manually check it out like so (without any symlinks): .<-- https://llvm.org/svn/llvm-project/llvm/branches/release_37 tools/clang <-- https://llvm.org/svn/llvm-project/cfe/branches/release_37 tools/clang/tools/extra <-- https://llvm.org/svn/llvm-project/clang-tools-extra/branches/release_37 I'll investigate, because it would be nice to have those tools. -Dimitry > On 21 Aug 2015, at 13:42, Nikola Smiljanic wrote: > > Hi Dmitry, if I understood Hans clang-extra wasn't part of the build prior to > rc3. Just delete it and run script with --no-checkout. > > On Fri, Aug 21, 2015 at 7:15 PM, Dimitry Andric wrote: > Hm, it does not seem to compile at all here? The build ends with: > > In file included from > /home/dim/llvm-3.7.0/rc3/llvm.src/tools/clang/tools/extra/clang-apply-replacements/lib/Tooling/ApplyReplacements.cpp:17: > /home/dim/llvm-3.7.0/rc3/llvm.src/tools/clang/tools/extra/clang-apply-replacements/lib/Tooling/../../include/clang-apply-replacements/Tooling/ApplyReplacements.h:19:10: > fatal error: 'clang/Tooling/Refactoring.h' file not found > #include "clang/Tooling/Refactoring.h" > ^ > 1 error generated. > > Any idea? I had no problems at all with -rc2. > > -Dimitry > > > On 21 Aug 2015, at 02:51, Hans Wennborg wrote: > > > > Hello everyone, > > > > 3.7-rc3 has just been tagged. Testers, please test, build binaries, > > upload to the sftp and report results to this thread. > > > > Again, a lot of patches got merged between rc2 and rc3, but hopefully > > nothing that should upset things. > > > > One thing that did change is that the release script now correctly > > symlinks clang-tools-extra into the build. If this causes problems on > > your platform, please just remove it. > > > > This is a release candidate in the real sense: at this point I have > > zero release blockers on my radar. I will now only accept fixes for > > critical regressions, and if nothing comes up, rc3 will be promoted to > > 3.7.0-final. > > > > Documentation and release note patches are still welcome all the way > > up until the final tag goes in. > > > > Issues that were on my radar, but I don't consider blocking: > > > > - Sanitizer test failures on various platforms, e.g. PR24222. We never > > ran these tests in previous releases, so it's not a regression. It > > would be great if the sanitizer folks could look into the test > > failures, but it's not blocking 3.7. > > > > - PR24273: "[ARM] Libc++abi built in-tree with libunwind fails in > > __cxa_allocate_exception", Renato will exclude libc++ from his build > > for now. > > > > - Lack of key functions in some Instruction classes causing build > > failures without -fno-rtti > > (http://lists.llvm.org/pipermail/llvm-dev/2015-August/089010.html). No > > patches have been forthcoming, so this will not get fixed for 3.7. At > > least we correctly report -fno-rtti in llvm-config built with CMake > > now. > > > > - r244221: "[SPARC] Don't compare arch name as a string, use the enum > > instead", owner is unresponsive. > > > > - "[lldb] r245020 - [MIPS]Handle floating point and aggregate return > > types in SysV-mips [32 bit] ABI", owner is unresponsive. > > > > > > Cheers, > > Hans > > signature.asc Description: Message signed with OpenPGP using GPGMail ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLDB for bare-iron targets lacking support for qC /qfThreadInfo packet
One option is to send a ? packet to get a stop reply packet back. The stop reply should contain a "thread:;" key/value pair and you could just make the pid == tid == . We currently try these in the order below: 1 - qProcessInfo 2 - qC 3 - qfThreadInfo Now we could add a fourth: 4 - ? > On Aug 21, 2015, at 12:23 AM, Jaydeep Patil wrote: > > Hi, > > The gdb-stub running on a MIPS bare-iron board lacks support for qC > /qfThreadInfo packet. Once the LLDB is connected to the target it cannot > proceed further as there is no process and/or thread information available > from the target. However GDB is able to debug the application as it ignores > the output of qC /qfThreadInfo packet if they are not supported. GDB assumes > that a process/thread X is available for debugging. > > Is there any way in LLDB to support such bare-iron targets where qC > /qfThreadInfo packets are not supported? > > Regards, > Jaydeep ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 24538] New: Tests that use throw/catch are broken on Windows due to lack of compiler support
https://llvm.org/bugs/show_bug.cgi?id=24538 Bug ID: 24538 Summary: Tests that use throw/catch are broken on Windows due to lack of compiler support Product: lldb Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: ztur...@google.com CC: llvm-b...@lists.llvm.org Blocks: 21766 Classification: Unclassified clang-cl does not yet properly support catch and throw, so any test executable which uses catch or throw cannot even compile with clang-cl. Exception support is almost complete, so once it is working we can re-enable these tests and try again. This affects the following tests: TestMultithreaded.test_breakpoint_callback TestMultithreaded.test_sb_api_listener_event_description TestMultithreaded.test_sb_api_listener_resume TestMultithreaded.test_sb_api_listener_event_process_state TestCPPExceptionBreakpoint.test_cpp_exception_breakpoint_with_dwarf TestCPPExceptionBreakpoints.test_with_dwarf -- 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] [3.7 Release] RC3 has been tagged, let's wrap this up
On Thu, Aug 20, 2015 at 5:51 PM, Hans Wennborg wrote: > Hello everyone, > > 3.7-rc3 has just been tagged. Testers, please test, build binaries, > upload to the sftp and report results to this thread. Windows binaries uploaded. sha1 sums: 1f0ad138830146aa3ea93561772b82e0b93c855d LLVM-3.7.0-rc3-win32.exe afb014481a46a6d354bb3c2fc2cac9c18b7a6776 LLVM-3.7.0-rc3-win64.exe Attaching the batch file I used for building. Thanks, Hans build_llvm_370._bat_ Description: Binary data ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [3.7 Release] RC3 has been tagged, let's wrap this up
AArch64 up. All green. On 21 August 2015 at 01:51, Hans Wennborg wrote: > Hello everyone, > > 3.7-rc3 has just been tagged. Testers, please test, build binaries, > upload to the sftp and report results to this thread. > > Again, a lot of patches got merged between rc2 and rc3, but hopefully > nothing that should upset things. > > One thing that did change is that the release script now correctly > symlinks clang-tools-extra into the build. If this causes problems on > your platform, please just remove it. > > This is a release candidate in the real sense: at this point I have > zero release blockers on my radar. I will now only accept fixes for > critical regressions, and if nothing comes up, rc3 will be promoted to > 3.7.0-final. > > Documentation and release note patches are still welcome all the way > up until the final tag goes in. > > Issues that were on my radar, but I don't consider blocking: > > - Sanitizer test failures on various platforms, e.g. PR24222. We never > ran these tests in previous releases, so it's not a regression. It > would be great if the sanitizer folks could look into the test > failures, but it's not blocking 3.7. > > - PR24273: "[ARM] Libc++abi built in-tree with libunwind fails in > __cxa_allocate_exception", Renato will exclude libc++ from his build > for now. > > - Lack of key functions in some Instruction classes causing build > failures without -fno-rtti > (http://lists.llvm.org/pipermail/llvm-dev/2015-August/089010.html). No > patches have been forthcoming, so this will not get fixed for 3.7. At > least we correctly report -fno-rtti in llvm-config built with CMake > now. > > - r244221: "[SPARC] Don't compare arch name as a string, use the enum > instead", owner is unresponsive. > > - "[lldb] r245020 - [MIPS]Handle floating point and aggregate return > types in SysV-mips [32 bit] ABI", owner is unresponsive. > > > Cheers, > Hans ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
