[lldb-dev] [Bug 21211] test_sb_api_listener_event_description (TestMultithreaded.SBBreakpointCallbackCase) failing on FreeBSD: expected state running, got state = launching
https://bugs.llvm.org/show_bug.cgi?id=21211 Michał Górny changed: What|Removed |Added Status|REOPENED|RESOLVED CC||mgo...@gentoo.org Resolution|--- |FIXED --- Comment #4 from Michał Górny --- The referenced diff is merged, and the test seems to pass for me right 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 48370] New: TestMultithreaded.py::test_python_stop_hook fails on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=48370 Bug ID: 48370 Summary: TestMultithreaded.py::test_python_stop_hook fails on FreeBSD Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: mgo...@gentoo.org CC: ema...@freebsd.org, jdevliegh...@apple.com, llvm-b...@lists.llvm.org == ERROR: test_python_stop_hook (TestMultithreaded.SBBreakpointCallbackCase) Test that you can run a python command in a stop-hook when stdin is File based. -- Traceback (most recent call last): File "/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/decorators.py", line 136, in wrapper return func(*args, **kwargs) File "/usr/home/mgorny/llvm-project/lldb/test/API/api/multithreaded/TestMultithreaded.py", line 38, in test_python_stop_hook 'test_python_stop_hook') File "/usr/home/mgorny/llvm-project/lldb/test/API/api/multithreaded/TestMultithreaded.py", line 117, in build_and_test check_call(exe, env=env, stdout=fnull, stderr=fnull) File "/usr/local/lib/python3.7/subprocess.py", line 363, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['/home/mgorny/llvm-project/_build/lldb-test-build.noindex/api/multithreaded/TestMultithreaded.test_python_stop_hook/test_python_stop_hook', '/home/mgorny/llvm-project/_build/lldb-test-build.noindex/api/multithreaded/TestMultithreaded.test_python_stop_hook/inferior_program']' returned non-zero exit status 1. Config=x86_64-/home/mgorny/llvm-project/_build/bin/clang -- 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 48371] New: LLDB needs a better way of expressing unavailable registers (test_register_commands failure)
https://bugs.llvm.org/show_bug.cgi?id=48371 Bug ID: 48371 Summary: LLDB needs a better way of expressing unavailable registers (test_register_commands failure) Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: mgo...@gentoo.org CC: ema...@freebsd.org, jdevliegh...@apple.com, llvm-b...@lists.llvm.org LLDB can currently only hide unavailable registers via manipulating the global register count, i.e. hide the last registers on the list. This doesn't work for FreeBSD and NetBSD, and could also be problematic as new CPUs emerge (or possibly already is). Unavailable registers not being hidden cause test_register_commands to fail: FAIL: test_register_commands (TestRegisters.RegisterCommandsTestCase) Test commands related to registers, in particular vector registers. -- Traceback (most recent call last): File "/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/decorators.py", line 136, in wrapper return func(*args, **kwargs) File "/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/decorators.py", line 136, in wrapper return func(*args, **kwargs) File "/usr/home/mgorny/llvm-project/lldb/test/API/commands/register/register/register_command/TestRegisters.py", line 41, in test_register_commands substrs=['registers were unavailable'], matching=False) File "/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 2573, in expect self.fail(log_msg) AssertionError: Ran command: "register read -a" Got output: General Purpose Registers: [...] Memory Protection Extensions: 6 registers were unavailable. [...] Not expecting sub string: "registers were unavailable" (was found) At least one expected register is unavailable. Config=x86_64-/home/mgorny/llvm-project/_build/bin/clang -- 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 48372] New: TestTargetCreateDeps.py failures on FreeBSD (and Linux)
https://bugs.llvm.org/show_bug.cgi?id=48372 Bug ID: 48372 Summary: TestTargetCreateDeps.py failures on FreeBSD (and Linux) Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: mgo...@gentoo.org CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org The original test comment says: #linux does not support loading dependent files, but android does I'm not sure if the same is true of FreeBSD but certainly it's not implemented yet. -- 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 48373] New: TestBreakpointInGlobalConstructors fails on FreeBSD (needs dyld fixes)
https://bugs.llvm.org/show_bug.cgi?id=48373 Bug ID: 48373 Summary: TestBreakpointInGlobalConstructors fails on FreeBSD (needs dyld fixes) Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: mgo...@gentoo.org CC: ema...@freebsd.org, jdevliegh...@apple.com, llvm-b...@lists.llvm.org The LLDB's dynamic loader support is currently oriented towards Linux behavior, i.e. reporting the dynamic loader itself on the first r_debug breakpoint hit, and then all DT_NEEDED libraries on a second hit. On FreeBSD there is only one hit for all the libraries. The relevant discussion can be found at: https://reviews.llvm.org/D92187 -- 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 48374] New: TestDeletedExecutable.py fails on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=48374
Bug ID: 48374
Summary: TestDeletedExecutable.py fails on FreeBSD
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: mgo...@gentoo.org
CC: ema...@freebsd.org, jdevliegh...@apple.com,
llvm-b...@lists.llvm.org
FAIL: test (TestDeletedExecutable.TestDeletedExecutable)
--
Traceback (most recent call last):
File
"/usr/home/mgorny/llvm-project/lldb/test/API/functionalities/deleted-executable/TestDeletedExecutable.py",
line 44, in test
self.runCmd("process attach -p " + str(popen.pid))
File
"/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 2184, in runCmd
msg if (msg) else CMD_MSG(cmd))
AssertionError: False is not True : Command 'process attach -p 2980
Error output:
error: attach failed: unable to find executable for
'/home/mgorny/llvm-project/_build/lldb-test-build.noindex/functionalities/deleted-executable/TestDeletedExecutable.test/a.out'
' did not return successfully
Config=x86_64-/home/mgorny/llvm-project/_build/bin/clang
--
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 48375] New: TestReturnValue.py test failures on FreeBSD/i386
https://bugs.llvm.org/show_bug.cgi?id=48375 Bug ID: 48375 Summary: TestReturnValue.py test failures on FreeBSD/i386 Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: mgo...@gentoo.org CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org The two following tests fail on FreeBSD/i386: test_with_python test_vector_values Apparently MacOS suffers from the same problem, and Linux did with old clang. -- 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 48376] New: TestCreateAfterAttach fails on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=48376 Bug ID: 48376 Summary: TestCreateAfterAttach fails on FreeBSD Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: mgo...@gentoo.org CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org FAIL: test_create_after_attach_dwarf (TestCreateAfterAttach.CreateAfterAttachTestCase) Test thread creation after process attach. -- Traceback (most recent call last): File "/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1853, in test_method return attrvalue(self) File "/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/decorators.py", line 136, in wrapper return func(*args, **kwargs) File "/usr/home/mgorny/llvm-project/lldb/test/API/functionalities/thread/create_after_attach/TestCreateAfterAttach.py", line 48, in test_create_after_attach self, "main.cpp", self.break_1, num_expected_locations=1) File "/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/lldbutil.py", line 426, in run_break_set_by_file_and_line num_locations=num_expected_locations) File "/usr/home/mgorny/llvm-project/lldb/packages/Python/lldbsuite/test/lldbutil.py", line 647, in check_breakpoint_result out_num_locations)) AssertionError: False is not True : Expecting 1 locations, got 2. Config=x86_64-/home/mgorny/llvm-project/_build/bin/clang This is probably related to https://reviews.llvm.org/D92264. -- 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] [Release-testers] LLVM 11.0.1-rc1 has been tagged
Hi, I finished testing llvm-11.0.1-rc1 on Power PC 64bit Little Endian for - Ubuntu 18.04 - Red Hat 7.4 I have uploaded the binaries from IBM. The sha1 files are attached. Thanks, Ahsan Saghir. On Thu, 26 Nov 2020 at 02:21, Tom Stellard via Release-testers < release-test...@lists.llvm.org> wrote: > Hi, > > I've tagged LLVM 11.0.1-rc1. Testers may begin testing and uploading > binaries. If you still have bugs you want fixed in LLVM 11.0.1, you > have until Dec. 8 to request backports. You can make these requests by > filing a bug at bugs.llvm.org and putting release-11.0.1 in the 'blocks' > field. > > -Tom > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > clang+llvm-11.0.1-rc1-powerpc64le-linux-rhel-7.4.sha1 Description: Binary data clang+llvm-11.0.1-rc1-powerpc64le-linux-ubuntu-18.04.sha1 Description: Binary data ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 48381] New: lldb not stopped at an executed return statement
https://bugs.llvm.org/show_bug.cgi?id=48381
Bug ID: 48381
Summary: lldb not stopped at an executed return statement
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: yangyib...@nju.edu.cn
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org
Created attachment 24232
--> https://bugs.llvm.org/attachment.cgi?id=24232&action=edit
the binary 'a.out'
$ clang -O1 -g small.c
$ lldb a.out
(lldb) target create "a.out"
Current executable set to '/root/DeVIL/a.out' (x86_64).
(lldb) b main
Breakpoint 1: where = a.out`main at small.c:14:10, address = 0x004004a0
(lldb) run
-> 14 for (; d < 1; d++)
(lldb) step
-> 15 for (; b < 1; b++)
(lldb) step
-> 16 *c[b][d + 1] = 0;
(lldb) step
-> 15 for (; b < 1; b++)
(lldb) step
-> 14 for (; d < 1; d++)
(lldb) step
-> 18 return 0;
(lldb)
$ lldb a.out
(lldb) target create "a.out"
Current executable set to '/root/DeVIL/a.out' (x86_64).
(lldb) b 18
Breakpoint 1: where = a.out`main + 10 at small.c:18:3, address =
0x004004aa
(lldb) run
Process 27027 launched: '/root/DeVIL/a.out' (x86_64)
Process 27027 exited with status = 0 (0x)
(lldb)
$ cat small.c
struct S
{
volatile int f;
} a;
unsigned int b;
static int *c[1][2] = {{0, (int *)&a.f}};
static unsigned int d;
int
main ()
{
for (; d < 1; d++)
for (; b < 1; b++)
*c[b][d + 1] = 0;
return 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 48382] New: lldb wrongly stopped at an unexecuted statement
https://bugs.llvm.org/show_bug.cgi?id=48382
Bug ID: 48382
Summary: lldb wrongly stopped at an unexecuted statement
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: yangyib...@nju.edu.cn
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org
Created attachment 24233
--> https://bugs.llvm.org/attachment.cgi?id=24233&action=edit
the binary 'a.out'
$ cat small.c
/* { dg-options "-O2" } */
/* { dg-do run } */
static const long long int TagTypeNumber = 0xll;
long long int x;
void foo(void)
{
x = TagTypeNumber + 1;
}
int main(int argc, char **argv)
{
if (argc > 0)
foo ();
if ((x & TagTypeNumber) == TagTypeNumber)
{
unsigned y = (unsigned)x;
__builtin_printf ("v: %u\n", y);
if (y != 1)
__builtin_abort ();
}
return 0;
}
$ clang -O2 -g small.c
$ lldb a.out
(lldb) target create "a.out"
Current executable set to '/root/DeVIL/a.out' (x86_64).
(lldb) b 16
Breakpoint 1: where = a.out`main + 45 at small.c:18:8, address =
0x0040058d
(lldb) r
Process 45445 launched: '/root/DeVIL/a.out' (x86_64)
v: 1
Process 45445 exited with status = 0 (0x)
(lldb)
# when step by step, lldb is wrongly stopped at line 16 as follows.
$ lldb a.out
(lldb) target create "a.out"
Current executable set to '/root/DeVIL/a.out' (x86_64).
(lldb) b main
Breakpoint 1: where = a.out`main + 11 at small.c:15:12, address =
0x0040056b
(lldb) r
13 int main(int argc, char **argv)
14 {
-> 15 if (argc > 0)
16 foo ();
17
(lldb) s
13 int main(int argc, char **argv)
14 {
15 if (argc > 0)
-> 16 foo ();
17
(lldb) s
8void foo(void)
9{
-> 10 x = TagTypeNumber + 1;
11 }
##
# clang and lldb versin
$ clang --version
Ubuntu clang version
12.0.0-++20201202063839+f0193623297-1~exp1~20201202174527.2077
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
$ lldb --version
lldb version 12.0.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
