wxWidgets Discussion Forum

it's an old story...
read this link about proper warnings.
viewtopic.php?f=19&t=46209
read there about -Wall -Wextra warnings. if it's gcc or clang. or find proper warnings for MS tools.

remove last comma in constructor param list
and write text to the control as *MainEditBox<<"test";

and show all your debugger diagnostics. problem looks like not from this lines.

it uses exactly the cmake as build front end and then uses gnu make or ninja as backend.
now i prefer an IDE couple clang+ninja in my designs.

i' have installed Ubuntu 16.04, with Unity and LXQT as desktops. I mostly work in lxqt, because it is quite lightweight. It's some standard dark GTK theme(I do not remember which), and in application i use two basic color variables - default_fore and default_back and play with them using Darker(..),...

Created by me just for fun(because i hate every ide i met in my life ) ).
screencast is here -
https://youtu.be/Ut677Vo2Sqs

menu bar is a special control. application frame has only one menubar(at least in Windows). that's why wxFrame has special method of assigning wxMenuBar to wxFrame. when you call SetMenuBar(...), you declare that this menuBar is assigned to this Frame. and Frame takes ownership of mentioned MenuBar,...

when you're giving a "parent" parameter to control constructor - it's your new control is added to parent's childs list. and when parent is deleted, it deletes in his destructor all the childs from this list. but if you did not give a parent - you must delete the control explicitly. it's standard be...

it looks like your gcc does not store unwinding info by default.
or may be you have some specific gcc options.

1.new creates objects on heap anyway, if it is not redefined globally or for a class. then it creates objects as redefined. 2.local in functions variabes are created(space reserved) on stack, if they are not declared as static - then they are created in global memory. 3. global variables are created...

muscle. i wrote a simple function of "native" stack dump using c++ stdlib. #include <execinfo.h> void dumpStack(){ const int max_entries = 1000; //let we try to unwind 1000 frames deep stack void* lbuf[max_entries]; //buffer for stack frames entries int lcnt = backtrace(lbuf, max_entries); //get fra...

it's ubuntu 16.04/Intel, desktop, not rasberry.
yes i've built wxWIdgets, but nothing special, with very common settings..just for dynamic link libraries.
compiler - g++.

I added to my app this crash logs, and in my case everything works fine. And all the stack is logged. but my stack is a way deeper than yours. <frame level="0" function="CodeBeeApp::OnFatalException()" offset="00000000" file="...." line="3048"/> <frame level="1"/> <frame level="2"/> <frame level="3"...

BTW, your gdb dump "after continue" shows that your frames are not unwound inside OnFatalException. and it looks like stack frames info must be available inside it. i never used this functionality of wxWidgets...you're getting info using addAll...but documentation for this function is not clear. for...

Yes, this crashes immediately but the crash log contains only: Code: Select all <stack> <frame level="0" function="COurApp::OnFatalException()" offset="0" address="0x5c360"/> <frame level="1" function="wxFatalSignalHandler" offset="0" address="0x3eb1a0"/> <frame level="2" function="__default_sa_res...

memcpy is innocent function if you previously checked size of destination buffer and size of data. here they checked and expanded buffer if needed, to hold all the data, and have appended data using memcpy. no problem. Actually, no one checks if the memory was allocated as expected. AFAIK Passing N...