Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » U++ community news and announcements » U++ 2019.1.rc4 released
U++ 2019.1.rc4 released [message #51554] Mon, 15 April 2019 08:23 Go to next message
mirek is currently offline  mirek
Messages: 11892
Registered: November 2005
Ultimate Member
Hi,

after a ministorm of bugs and fixes, we are now at rc4.

https://sourceforge.net/projects/upp/files/upp/2019.1.rc4/

Thinks fixed and added:

- Support for Visual C++ / Build Tools 2019
- MacOS version does not require crypto.dylib installed to run theide
- Fixed issue in theide help (multiplying entries for topics with TOC)
- Mingw (and, in fact GCC and CLANG) now support "SO" compilation (compiles packages to .dll/.so/.dylib, this helps with linking speed)

Thanks for testing!

Mirek

[Updated on: Mon, 15 April 2019 08:24]

Report message to a moderator

Re: U++ 2019.1.rc4 released [message #51555 is a reply to message #51554] Mon, 15 April 2019 08:54 Go to previous messageGo to next message
koldo is currently offline  koldo
Messages: 2959
Registered: August 2008
Veteran
Thank you all for your great job Smile Smile

Best regards
IƱaki
Re: U++ 2019.1.rc4 released [message #51557 is a reply to message #51554] Tue, 16 April 2019 08:39 Go to previous messageGo to next message
Tom1
Messages: 618
Registered: March 2007
Contributor
Hi,

I have now tested rc4 (on Windows 10 1809 / 64-bit with my own application code) and everything seems to work fine. Smile

Thanks and best regards,

Tom
Re: U++ 2019.1.rc4 released [message #51568 is a reply to message #51557] Wed, 17 April 2019 14:48 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1391
Registered: September 2007
Senior Contributor
Will test it ASAP. Takes a couple of days to merge all my forks into the main release...
Re: U++ 2019.1.rc4 released [message #51572 is a reply to message #51568] Wed, 17 April 2019 21:31 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 817
Registered: December 2006
Experienced Contributor
I was investigating a crash with TheIDE and discovered a bunch of uninitialized memory reads. Please check an attached file.
  • Attachment: vg.log
    (Size: 365.15KB, Downloaded 13 times)


Regards,
Novo
Re: U++ 2019.1.rc4 released [message #51573 is a reply to message #51554] Wed, 17 April 2019 23:43 Go to previous messageGo to next message
forlano is currently offline  forlano
Messages: 1055
Registered: March 2006
Location: Italy
Experienced Contributor
Hi Mirek,

the Mac OS version seems to work properly.
Thanks,
Luigi
Re: U++ 2019.1.rc4 released [message #51574 is a reply to message #51573] Thu, 18 April 2019 00:22 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 817
Registered: December 2006
Experienced Contributor
I'm getting a random crash with TheIDE (every second time I launch it) with the call stack below. (Full rebuild)

#0  0x0000555555879007 in SkipGdbInfo(Upp::CParser&) (p=...) at /home/ssg/dvlp/cpp/upp/git/uppsrc/ide/Debuggers/GdbData.cpp:8
#1  0x000055555587a7d8 in DataClean(Upp::CParser&) (p=...) at /home/ssg/dvlp/cpp/upp/git/uppsrc/ide/Debuggers/GdbData.cpp:63
#2  0x000055555587ac13 in DataClean(char const*) (s=<optimized out>) at /home/ssg/dvlp/cpp/upp/git/uppsrc/ide/Debuggers/GdbData.cpp:79
#3  0x000055555587fac2 in Gdb::TryAuto(Upp::Index<Upp::String>&, Upp::String const&) (this=0x7fffde4e4030, tested=..., exp=...)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/Core/String.h:313
#4  0x000055555587fd69 in Gdb::Autos() (this=0x7fffde4e4030) at /home/ssg/dvlp/cpp/upp/git/uppsrc/ide/Debuggers/GdbData.cpp:172
#5  0x0000555555883dd9 in Gdb::Cmdp(char const*, bool, bool)
    (this=0x7fffde4e4030, cmdline=<optimized out>, fr=<optimized out>, setframe=<optimized out>)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/ide/Debuggers/Gdb.cpp:292
#6  0x000055555588470a in Gdb::Step(char const*) (this=0x7fffde4e4030, cmd=0x555555f18f84 "next")
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/ide/Debuggers/Gdb.cpp:453
#7  0x00005555558fcb7d in Upp::Function<void ()>::operator()() const (this=<optimized out>) at /home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Function.h:76
#8  0x00005555558fcb7d in Upp::Bar::ScanKeys::Do(unsigned int) (k=131015, this=0x7ffffffcad10)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlLib/Bar.cpp:509
#9  0x00005555558fcb7d in Upp::Bar::Scan(Upp::Function<void (Upp::Bar&)>, unsigned int) (proc=..., key=131015)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlLib/Bar.cpp:520
#10 0x00005555558fd26f in Upp::TopSubMenuItem::HotKey(unsigned int) (this=0x7ffff3a05080, key=131015) at /usr/include/c++/8/bits/atomic_base.h:299
#11 0x0000555555bf1d15 in Upp::Ctrl::HotKey(unsigned int) (this=<optimized out>, key=131015)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/CtrlCore.h:1113
#12 0x0000555555bf1d15 in Upp::Ctrl::HotKey(unsigned int) (this=this@entry=0x7ffffffccb70, key=key@entry=131015)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/CtrlCore.h:1113
#13 0x00005555559191f2 in Upp::MenuBar::HotKey(unsigned int) (this=0x7ffffffccb70, key=131015)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlLib/MenuBar.cpp:433
#14 0x0000555555bf1d15 in Upp::Ctrl::HotKey(unsigned int) (this=<optimized out>, key=131015)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/CtrlCore.h:1113
#15 0x0000555555bf1d15 in Upp::Ctrl::HotKey(unsigned int) (this=<optimized out>, key=131015)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/CtrlCore.h:1113
#16 0x0000555555bf5010 in Upp::Ctrl::DispatchKey(unsigned int, int) (keycode=131015, count=1) at /home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Ptr.h:43
#17 0x0000555555c0b945 in Upp::Ctrl::Proc() (this=<optimized out>) at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/GtkEvent.cpp:485
#18 0x0000555555c0c78f in Upp::Ctrl::ProcessEvent0(bool*, bool) (quit=0x0, fetch=<optimized out>)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/GtkEvent.cpp:557
#19 0x0000555555c0cd21 in Upp::Ctrl::ProcessEvents0(bool*, bool) (fetch=fetch@entry=true, quit=0x0)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/GtkEvent.cpp:583
#20 0x0000555555c0d50d in Upp::Ctrl::ProcessEvents(bool*) (quit=0x0) at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/GtkEvent.cpp:631
#21 0x0000555555c0d50d in Upp::Ctrl::EventLoop(Upp::Ctrl*) (ctrl=0x7ffffffcb380) at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/GtkEvent.cpp:631
#22 0x0000555555c15a71 in Upp::TopWindow::Run(bool) (this=this@entry=0x7ffffffcb380, appmodal=appmodal@entry=false)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlCore/TopWindow.cpp:324
#23 0x0000555555811f1e in GuiMainFn_() () at /home/ssg/dvlp/cpp/upp/git/uppsrc/ide/main.cpp:305
#24 0x0000555555710d08 in main(int, char**, char const**) (argc=1, argv=0x7fffffffdef8, envptr=0x55555628b2f0)
    at /home/ssg/dvlp/cpp/upp/git/uppsrc/ide/main.cpp:120

It is most likely related to uninitialized memory reads or corrupted memory.


Regards,
Novo
Re: U++ 2019.1.rc4 released [message #51575 is a reply to message #51574] Thu, 18 April 2019 07:59 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 11892
Registered: November 2005
Ultimate Member
Novo wrote on Thu, 18 April 2019 00:22
I'm getting a random crash with TheIDE (every second time I launch it) with the call stack below. (Full rebuild)


Thanks. It would be really helpful to provide info about host platform and steps to reproduce.

From the call stack it looks like like crash in Gdb interface. Does it happen when trying to debug something?

Mirek
Re: U++ 2019.1.rc4 released [message #51576 is a reply to message #51574] Thu, 18 April 2019 08:03 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 11892
Registered: November 2005
Ultimate Member
Novo wrote on Thu, 18 April 2019 00:22
I'm getting a random crash with TheIDE (every second time I launch it) with the call stack below. (Full rebuild)
It is most likely related to uninitialized memory reads or corrupted memory.


Based on stack dump, hopefully fixed in trunk. Please test.

Mirek
Re: U++ 2019.1.rc4 released [message #51578 is a reply to message #51576] Thu, 18 April 2019 10:17 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1391
Registered: September 2007
Senior Contributor
Weirdly I got a compilation error in some code that hasn't been touched in years related to variable shadowing...

Something must have changed in the way the C++ compiler is invoked.

Not a real problem though, it is better to not shadow so I renamed the variables.

My projects are made out of multiple executable and usually I have multiple TheIDEs running (3+), but this new release has a blazing fast "open main package".

I tested the command line stuff. No issues.

Next I'll test GUI.

Is there a a way to force dark mode under Windows? I have code editor colors for dark mode, but they always looked out of place with light UI.
Re: U++ 2019.1.rc4 released [message #51579 is a reply to message #51578] Thu, 18 April 2019 10:30 Go to previous messageGo to next message
Tom1
Messages: 618
Registered: March 2007
Contributor
Hi cbpporter,

Dark theme is enabled in Windows 10 using Settings > Colors > Choose your default app mode > Dark

Then restart TheIDE.

Best regards,

Tom
Re: U++ 2019.1.rc4 released [message #51580 is a reply to message #51572] Thu, 18 April 2019 10:53 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 11892
Registered: November 2005
Ultimate Member
Novo wrote on Wed, 17 April 2019 21:31
I was investigating a crash with TheIDE and discovered a bunch of uninitialized memory reads. Please check an attached file.


Should be all fixed in the trunk.

All of it was innocent things like Enabling/Disableing random buttons in theide toolbar during initialization, then it got fixed by second SetBar call even before theide is open.

That said, it is definitely better if theide runs valgrind clean, so I from now on I will do valgrind checks before each release. Thank you.

Mirek
Re: U++ 2019.1.rc4 released [message #51597 is a reply to message #51576] Thu, 18 April 2019 22:20 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 817
Registered: December 2006
Experienced Contributor
mirek wrote on Thu, 18 April 2019 02:03
Novo wrote on Thu, 18 April 2019 00:22
I'm getting a random crash with TheIDE (every second time I launch it) with the call stack below. (Full rebuild)
It is most likely related to uninitialized memory reads or corrupted memory.


Based on stack dump, hopefully fixed in trunk. Please test.

Mirek

Thank you! So far everything seems to work fine.


Regards,
Novo
Re: U++ 2019.1.rc4 released [message #51598 is a reply to message #51580] Fri, 19 April 2019 00:32 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 817
Registered: December 2006
Experienced Contributor
mirek wrote on Thu, 18 April 2019 04:53
Novo wrote on Wed, 17 April 2019 21:31
I was investigating a crash with TheIDE and discovered a bunch of uninitialized memory reads. Please check an attached file.


Should be all fixed in the trunk.

All of it was innocent things like Enabling/Disableing random buttons in theide toolbar during initialization, then it got fixed by second SetBar call even before theide is open.

That said, it is definitely better if theide runs valgrind clean, so I from now on I will do valgrind checks before each release. Thank you.

Mirek

Thank you! Below are two more fixes which make TheIDE 100% valgrind-clean.
(I fixed/added two constructors)
	CppItem() : access(), kind(), at(), virt(), decla(), lvalue(), isptr(), filetype(), impl(), file(), line(), qualify(true) {}

struct PPItem {
	PPItem() : type(), segment_id() {}

These changes won't make TheIDE any slower.
This is C++98 initialization style. I didn't do that C++11 way for compatibility reason.


Regards,
Novo
Re: U++ 2019.1.rc4 released [message #51601 is a reply to message #51598] Fri, 19 April 2019 12:27 Go to previous messageGo to next message
mirek is currently offline  mirek
Messages: 11892
Registered: November 2005
Ultimate Member
Novo wrote on Fri, 19 April 2019 00:32
mirek wrote on Thu, 18 April 2019 04:53
Novo wrote on Wed, 17 April 2019 21:31
I was investigating a crash with TheIDE and discovered a bunch of uninitialized memory reads. Please check an attached file.


Should be all fixed in the trunk.

All of it was innocent things like Enabling/Disableing random buttons in theide toolbar during initialization, then it got fixed by second SetBar call even before theide is open.

That said, it is definitely better if theide runs valgrind clean, so I from now on I will do valgrind checks before each release. Thank you.

Mirek

Thank you! Below are two more fixes which make TheIDE 100% valgrind-clean.


Did it trigger any valgrind errors? If so, which ones?

Quote:

(I fixed/added two constructors)
	CppItem() : access(), kind(), at(), virt(), decla(), lvalue(), isptr(), filetype(), impl(), file(), line(), qualify(true) {}

struct PPItem {
	PPItem() : type(), segment_id() {}

These changes won't make TheIDE any slower.


Probably not noticeably, but it is matter of principle: Do I need from now on to initialize variables that are not used in particular branch of code?

Quote:

This is C++98 initialization style. I didn't do that C++11 way for compatibility reason.


Why? Smile

Mirek
Re: U++ 2019.1.rc4 released [message #51612 is a reply to message #51601] Fri, 19 April 2019 16:43 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 817
Registered: December 2006
Experienced Contributor
mirek wrote on Fri, 19 April 2019 06:27

Did it trigger any valgrind errors? If so, which ones?

Yes, they did. Please check the attached file.

mirek wrote on Fri, 19 April 2019 06:27

Quote:

(I fixed/added two constructors)
	CppItem() : access(), kind(), at(), virt(), decla(), lvalue(), isptr(), filetype(), impl(), file(), line(), qualify(true) {}

struct PPItem {
	PPItem() : type(), segment_id() {}

These changes won't make TheIDE any slower.


Probably not noticeably, but it is matter of principle: Do I need from now on to initialize variables that are not used in particular branch of code?

Well, valgrind and sanitizers is very often the only way to figure out an origin of a problem because sometimes this can be a bug with a compiler but the code itself. An when I see a lot of garbage in the output I just want to stop using the code because it is unprofessional. It is not that hard to fix all errors reported by valgrind and sanitizers.

In the second case both members are used, I believe.
In the first case I initialized everything because I didn't have time to figure out which one exactly is used uninitialized.

mirek wrote on Fri, 19 April 2019 06:27

Quote:

This is C++98 initialization style. I didn't do that C++11 way for compatibility reason.


Why? Smile

Old habit.
  • Attachment: vg.log.02
    (Size: 366.17KB, Downloaded 7 times)


Regards,
Novo
Re: U++ 2019.1.rc4 released [message #51613 is a reply to message #51612] Fri, 19 April 2019 16:53 Go to previous messageGo to next message
cbpporter is currently offline  cbpporter
Messages: 1391
Registered: September 2007
Senior Contributor
It would be great if "Output mode/Target file override" would be made package specific Smile.

Currently, you open package A, compile with "Target file override" into the desired location, open up a random package from examples, compile and your old executable from another project is overwritten.
Re: U++ 2019.1.rc4 released [message #51615 is a reply to message #51554] Sat, 20 April 2019 00:33 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 817
Registered: December 2006
Experienced Contributor
I do not know what is wrong with the GUI_APP_MAIN, but I'm getting 1.2 Mb of complains from valgrind. Please check attached file.
  • Attachment: vg.log
    (Size: 1.23MB, Downloaded 7 times)


Regards,
Novo
Re: U++ 2019.1.rc4 released [message #51616 is a reply to message #51554] Sat, 20 April 2019 00:51 Go to previous messageGo to next message
Novo is currently offline  Novo
Messages: 817
Registered: December 2006
Experienced Contributor
I do not know who is responsible for this crash (libfontconfig.so.1+0xdb67 or /uppsrc/Draw/Font.cpp:34:10), but I cannot even get close to my own code.
Memory Sanitizer:
Uninitialized bytes in __interceptor_strlen at offset 0 inside [0x7010000008a0, 11)
==30845==WARNING: MemorySanitizer: use-of-uninitialized-value
    #0 0x7f3bb6714097  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0xb097)
    #1 0x7f3bb6716baa in FcConfigFilename (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0xdbaa)
    #2 0x7f3bb672f607  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x26607)
    #3 0x7f3bb6721be3  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x18be3)
    #4 0x7f3bb6721e45  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x18e45)
    #5 0x7f3bb6714736  (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0xb736)
    #6 0x7f3bb6721f05 in FcInitBringUptoDate (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x18f05)
    #7 0x7f3bb6724be9 in FcFontList (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x1bbe9)
    #8 0x292ed45 in Upp::GetAllFacesSys() /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/FontFc.cpp:236:18
    #9 0x292e354 in Upp::Font::FaceList() /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/Font.cpp:34:10
    #10 0x292fc97 in Upp::sInitFonts() /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/Font.cpp:42:2
    #11 0x292fd68 in Upp::s__sF0_46_fn() /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/Font.cpp:47:2
    #12 0x12bb799 in Upp::Callinit::Callinit(void (*)(), char const*, int) /home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Defs.h:176:83
    #13 0x469944 in __cxx_global_var_init.4 /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/Font.cpp:46:1
    #14 0x469d5c in _GLOBAL__sub_I__blitz.cpp /home/ssg/dvlp/cpp/upp/git/out/MyApps/Draw/CLANGcpp17msan.Debug.Debug_Full.Gui.Shared.Usemalloc/$blitz.cpp
    #15 0x3dfd874 in __libc_csu_init (/home/ssg/dvlp/cpp/upp/git/out/MyApps/CLANGcpp17msan.Debug.Debug_Full.Gui.Shared.Usemalloc/OpenCorpora+0x3dfd874)
    #16 0x7f3bb47a0029 in __libc_start_main /build/glibc-B9XfQf/glibc-2.28/csu/../csu/libc-start.c:264:6
    #17 0x471839 in _start (/home/ssg/dvlp/cpp/upp/git/out/MyApps/CLANGcpp17msan.Debug.Debug_Full.Gui.Shared.Usemalloc/OpenCorpora+0x471839)

  Uninitialized value was created by a heap allocation
    #0 0x47adfc in __interceptor_malloc (/home/ssg/dvlp/cpp/upp/git/out/MyApps/CLANGcpp17msan.Debug.Debug_Full.Gui.Shared.Usemalloc/OpenCorpora+0x47adfc)
    #1 0x7f3bb6716b67 in FcConfigFilename (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0xdb67)
    #2 0x292e354 in Upp::Font::FaceList() /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/Font.cpp:34:10
    #3 0x292fc97 in Upp::sInitFonts() /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/Font.cpp:42:2
    #4 0x292fd68 in Upp::s__sF0_46_fn() /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/Font.cpp:47:2
    #5 0x12bb799 in Upp::Callinit::Callinit(void (*)(), char const*, int) /home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Defs.h:176:83
    #6 0x469944 in __cxx_global_var_init.4 /home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/Font.cpp:46:1
    #7 0x469d5c in _GLOBAL__sub_I__blitz.cpp /home/ssg/dvlp/cpp/upp/git/out/MyApps/Draw/CLANGcpp17msan.Debug.Debug_Full.Gui.Shared.Usemalloc/$blitz.cpp
    #8 0x3dfd874 in __libc_csu_init (/home/ssg/dvlp/cpp/upp/git/out/MyApps/CLANGcpp17msan.Debug.Debug_Full.Gui.Shared.Usemalloc/OpenCorpora+0x3dfd874)

SUMMARY: MemorySanitizer: use-of-uninitialized-value (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0xb097) 
Exiting


Regards,
Novo
Re: U++ 2019.1.rc4 released [message #51618 is a reply to message #51554] Sat, 20 April 2019 00:57 Go to previous messageGo to previous message
Novo is currently offline  Novo
Messages: 817
Registered: December 2006
Experienced Contributor
/home/ssg/dvlp/cpp/upp/git/uppsrc/Core/lheap.cpp:46:18: runtime error: index -1 out of bounds for type 'Upp::word [77]'
/home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Hash.cpp:307:33: runtime error: load of misaligned address 0x0000027ed2a3 for type 'const unsigned int', which requires 4 byte alignment
0x0000027ed2a3: note: pointer points here
 74  2e 68 00 28 64 65 66 61  75 6c 74 29 00 28 70 65  72 20 64 65 66 65 63 74  65 29 00 28 76 c3 bd
              ^ 
/home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Ops.h:3:51: runtime error: load of misaligned address 0x00000288de89 for type 'const Upp::dword' (aka 'const unsigned int'), which requires 4 byte alignment
0x00000288de89: note: pointer points here
 61 6e 73  2d 73 65 72 69 66 00 41  72 69 61 6c 00 e6 96 b0  e5 ae 8b e4 bd 93 00 53  69 6d 53 75 6e
              ^ 
/home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Ops.h:7:55: runtime error: store to misaligned address 0x7f1e14817182 for type 'Upp::dword' (aka 'unsigned int'), which requires 4 byte alignment
0x7f1e14817182: note: pointer points here
 65 65  46 72 65 65 46 72 65 65  46 72 65 65 46 72 65 65  46 72 65 65 46 72 65 65  46 72 65 65 46 72
              ^ 
/home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Ops.h:2:51: runtime error: load of misaligned address 0x7f1e102b4699 for type 'const Upp::word' (aka 'const unsigned short'), which requires 2 byte alignment
0x7f1e102b4699: note: pointer points here
 42 00 00  00 0d 00 0d 00 01 00 01  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 b2 b2 be ff
              ^ 
/home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/RescaleFilter.cpp:70:32: runtime error: left shift of negative value -5
/home/ssg/dvlp/cpp/upp/git/uppsrc/Draw/RescaleFilter.cpp:88:31: runtime error: left shift of negative value -5
/home/ssg/dvlp/cpp/upp/git/uppsrc/CtrlLib/ChGtk0.cpp:478:16: runtime error: index 30 out of bounds for type 'GdkColor [5]'
/home/ssg/dvlp/cpp/upp/git/uppsrc/Core/Other.h:294:71: runtime error: downcast of address 0x7ffe8dc05f98 which does not point to an object of type 'Upp::DisplayPopup'
0x7ffe8dc05f98: note: object is of type 'Upp::Ctrl'
 00 00 00 80  20 bd 85 02 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00
              ^~~~~~~~~~~~~~~~~~~~~~~
              vptr for 'Upp::Ctrl'
/usr/bin/xmessage
Segmentation fault (core dumped)

This time this is UB Sanitizer ... Smile


Regards,
Novo
Previous Topic: Dark theme support changes
Next Topic: U++ 2019.1.rc1 released
Goto Forum:
  


Current Time: Thu Jun 20 07:07:16 CEST 2019

Total time taken to generate the page: 0.01233 seconds