|
|
Home » Community » U++ community news and announcements » 2024rc
|
|
|
|
|
Re: 2024rc3 [message #61102 is a reply to message #61084] |
Mon, 18 November 2024 13:47   |
cbpporter
Messages: 1427 Registered: September 2007
|
Ultimate Contributor |
|
|
mirek wrote on Mon, 11 November 2024 11:15cbpporter wrote on Mon, 11 November 2024 10:08Tested on fresh install on another PC, and one common problem is back: CLANG marks my source file with error, with a red exlamation mark in the top elft corner, with the text "Errors".
It has no tooltip or click to tell you what the errors are.
You should see it in scrollbar.
Quote:
This is extremely common and comes and goes, and is very annoying because first it has a big red exclamation mark on your file, then it kills "IntelliSense".
This time it was triggered by a code like this (and many other cases):
String fullName = name;
fullName << ".";

I attached the error.
This probably means some problem of libclang installation. A good way to check is to activate "Assist diagnostics" and then Assist / "Current file parse errors" (post it here).
Sorry for being late, I had to locate the non main dev PCs where this problems occurs since on my mains (where VS is not detected, unrelated) it does not.
Errors do appear in the scrollbar but there is no tooltip. Nor on the exclamation bar. But they do appear in code.
Anyway, the one main problem that appears in all the assist diagnostic logs is:
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (35): use of undeclared identifier 'char32_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (58): use of undeclared identifier 'char16_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (59): use of undeclared identifier 'char32_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (77): use of undeclared identifier 'char16_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (78): use of undeclared identifier 'char32_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (92): unknown type name 'u16string'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (93): unknown type name 'u32string'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (102): no type named 'u16string' in namespace 'std::pmr'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (103): no type named 'u32string' in namespace 'std::pmr'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__functional\hash.h (371): use of undeclared identifier 'char16_t'
The rest seems to be related to String, so they might disappear if this one does.
This is on RC3 and RC4.
But for a more testable solution, in AddressBook.cpp, I've attached the output.
-
Attachment: parse_errors
(Size: 15.91KB, Downloaded 56 times)
|
|
|
|
|
Re: 2024rc3 [message #61105 is a reply to message #61102] |
Mon, 18 November 2024 14:02   |
 |
mirek
Messages: 14261 Registered: November 2005
|
Ultimate Member |
|
|
cbpporter wrote on Mon, 18 November 2024 13:47mirek wrote on Mon, 11 November 2024 11:15cbpporter wrote on Mon, 11 November 2024 10:08Tested on fresh install on another PC, and one common problem is back: CLANG marks my source file with error, with a red exlamation mark in the top elft corner, with the text "Errors".
It has no tooltip or click to tell you what the errors are.
You should see it in scrollbar.
Quote:
This is extremely common and comes and goes, and is very annoying because first it has a big red exclamation mark on your file, then it kills "IntelliSense".
This time it was triggered by a code like this (and many other cases):
String fullName = name;
fullName << ".";

I attached the error.
This probably means some problem of libclang installation. A good way to check is to activate "Assist diagnostics" and then Assist / "Current file parse errors" (post it here).
Sorry for being late, I had to locate the non main dev PCs where this problems occurs since on my mains (where VS is not detected, unrelated) it does not.
Errors do appear in the scrollbar but there is no tooltip. Nor on the exclamation bar. But they do appear in code.
Anyway, the one main problem that appears in all the assist diagnostic logs is:
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (35): use of undeclared identifier 'char32_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (58): use of undeclared identifier 'char16_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (59): use of undeclared identifier 'char32_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (77): use of undeclared identifier 'char16_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (78): use of undeclared identifier 'char32_t'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (92): unknown type name 'u16string'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (93): unknown type name 'u32string'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (102): no type named 'u16string' in namespace 'std::pmr'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__fwd\string.h (103): no type named 'u32string' in namespace 'std::pmr'
ERROR: C:\Dev\upprc4\bin\clang\include\c++\v1\__functional\hash.h (371): use of undeclared identifier 'char16_t'
The rest seems to be related to String, so they might disappear if this one does.
This is on RC3 and RC4.
But for a more testable solution, in AddressBook.cpp, I've attached the output.
Well, going to libclang comes with price - I do not already have control over bad installations. This is clearly one of those case where something happened to include path.
Mirek
|
|
|
|
|
Re: 2024rc3 [message #61128 is a reply to message #61109] |
Wed, 20 November 2024 20:42   |
Novo
Messages: 1430 Registered: December 2006
|
Ultimate Contributor |
|
|
Latest src.
$ cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.12.12
PRETTY_NAME="Alpine Linux v3.12"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"
$ clang --version
Alpine clang version 10.0.0 (https://gitlab.alpinelinux.org/alpine/aports.git 7445adce501f8473efdb93b17b5eaf2f1445ed4c)
Target: x86_64-alpine-linux-musl
Thread model: posix
InstalledDir: /usr/bin
Application: CParser (.cache/upp.out/CLANG.Debug.Debug_Full.Shared/CParser)
$ ./CParser
Segmentation fault
$ gdb ./CParser
#0 0x00005555555f34c8 in std::atomic<bool>::load (this=<error reading variable: Cannot access memory at address 0x7fffff7feff0>,
__m=<error reading variable: Cannot access memory at address 0x7fffff7fefec>)
at /usr/bin/../lib/gcc/x86_64-alpine-linux-musl/9.3.0/../../../../include/c++/9.3.0/atomic:113
#1 0x000055555560fcbf in Upp::StaticPrimitive_<Upp::Mutex>::Get (this=0x555555779a80 <Upp::Heap::mutex>) at Mt.h:326
#2 0x00005555556476d8 in Upp::StaticMutex::Enter (this=0x555555779a80 <Upp::Heap::mutex>) at Mt.h:333
#3 0x000055555564e4f0 in Upp::EnterHeapMutex () at sheap.cpp:377
#4 0x000055555564f9a4 in Upp::CurrentHeap::CurrentHeap (this=0x7fffff7ff0f8) at sheap.cpp:421
#5 0x000055555564e7a9 in Upp::MemoryAllocSz_ (sz=@0x7fffff7ff190: 60) at sheap.cpp:458
#6 0x00005555556534ad in Upp::MemoryAllocSz (size=@0x7fffff7ff190: 60) at heapdbg.cpp:142
#7 0x0000555555653572 in Upp::MemoryAlloc (size=60) at heapdbg.cpp:155
#8 0x0000555555652d39 in operator new (size=24) at heap.cpp:295
#9 0x00007ffff7e71440 in __cxa_thread_atexit () from /usr/lib/libstdc++.so.6
#10 0x000055555564e57b in Upp::MakeHeap () at sheap.cpp:403
#11 0x000055555564f9b0 in Upp::CurrentHeap::CurrentHeap (this=0x7fffff7ff288) at sheap.cpp:423
#12 0x000055555564e7a9 in Upp::MemoryAllocSz_ (sz=@0x7fffff7ff320: 60) at sheap.cpp:458
#13 0x00005555556534ad in Upp::MemoryAllocSz (size=@0x7fffff7ff320: 60) at heapdbg.cpp:142
#14 0x0000555555653572 in Upp::MemoryAlloc (size=60) at heapdbg.cpp:155
#15 0x0000555555652d39 in operator new (size=24) at heap.cpp:295
#16 0x00007ffff7e71440 in __cxa_thread_atexit () from /usr/lib/libstdc++.so.6
#17 0x000055555564e57b in Upp::MakeHeap () at sheap.cpp:403
#18 0x000055555564f9b0 in Upp::CurrentHeap::CurrentHeap (this=0x7fffff7ff418) at sheap.cpp:423
#19 0x000055555564e7a9 in Upp::MemoryAllocSz_ (sz=@0x7fffff7ff4b0: 60) at sheap.cpp:458
#20 0x00005555556534ad in Upp::MemoryAllocSz (size=@0x7fffff7ff4b0: 60) at heapdbg.cpp:142
#21 0x0000555555653572 in Upp::MemoryAlloc (size=60) at heapdbg.cpp:155
#22 0x0000555555652d39 in operator new (size=24) at heap.cpp:295
#23 0x00007ffff7e71440 in __cxa_thread_atexit () from /usr/lib/libstdc++.so.6
#24 0x000055555564e57b in Upp::MakeHeap () at sheap.cpp:403
#25 0x000055555564f9b0 in Upp::CurrentHeap::CurrentHeap (this=0x7fffff7ff5a8) at sheap.cpp:423
#26 0x000055555564e7a9 in Upp::MemoryAllocSz_ (sz=@0x7fffff7ff640: 60) at sheap.cpp:458
#27 0x00005555556534ad in Upp::MemoryAllocSz (size=@0x7fffff7ff640: 60) at heapdbg.cpp:142
#28 0x0000555555653572 in Upp::MemoryAlloc (size=60) at heapdbg.cpp:155
#29 0x0000555555652d39 in operator new (size=24) at heap.cpp:295
#30 0x00007ffff7e71440 in __cxa_thread_atexit () from /usr/lib/libstdc++.so.6
#31 0x000055555564e57b in Upp::MakeHeap () at sheap.cpp:403
#32 0x000055555564f9b0 in Upp::CurrentHeap::CurrentHeap (this=0x7fffff7ff738) at sheap.cpp:423
#33 0x000055555564e7a9 in Upp::MemoryAllocSz_ (sz=@0x7fffff7ff7d0: 60) at sheap.cpp:458
#34 0x00005555556534ad in Upp::MemoryAllocSz (size=@0x7fffff7ff7d0: 60) at heapdbg.cpp:142
#35 0x0000555555653572 in Upp::MemoryAlloc (size=60) at heapdbg.cpp:155
#36 0x0000555555652d39 in operator new (size=24) at heap.cpp:295
#37 0x00007ffff7e71440 in __cxa_thread_atexit () from /usr/lib/libstdc++.so.6
#38 0x000055555564e57b in Upp::MakeHeap () at sheap.cpp:403
#39 0x000055555564f9b0 in Upp::CurrentHeap::CurrentHeap (this=0x7fffff7ff8c8) at sheap.cpp:423
#40 0x000055555564e7a9 in Upp::MemoryAllocSz_ (sz=@0x7fffff7ff960: 60) at sheap.cpp:458
#41 0x00005555556534ad in Upp::MemoryAllocSz (size=@0x7fffff7ff960: 60) at heapdbg.cpp:142
#42 0x0000555555653572 in Upp::MemoryAlloc (size=60) at heapdbg.cpp:155
#43 0x0000555555652d39 in operator new (size=24) at heap.cpp:295
#44 0x00007ffff7e71440 in __cxa_thread_atexit () from /usr/lib/libstdc++.so.6
I understand that this is an old version of a compiler. But if I roll back Upp source code approximately four years back, then everything works just fine.
Regards,
Novo
|
|
|
|
|
Re: 2024rc3 [message #61132 is a reply to message #61131] |
Thu, 21 November 2024 18:48   |
Novo
Messages: 1430 Registered: December 2006
|
Ultimate Contributor |
|
|
mirek wrote on Thu, 21 November 2024 04:31Looks like a problem with thread_local implementation.
Mirek
Everything is fine now.
Thanks!
Regards,
Novo
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Sun Jun 08 22:27:44 CEST 2025
Total time taken to generate the page: 0.04891 seconds
|
|
|