Home » Extra libraries, Code snippets, applications etc. » OS Problems etc., Win32, POSIX, MacOS, FreeBSD, X11 etc » Untrivial EditString bug(?) in FreeBSD(and may be all POSIX)
| Untrivial EditString bug(?) in FreeBSD(and may be all POSIX) [message #20725] |
Wed, 01 April 2009 23:21  |
Mindtraveller
Messages: 917
Registered: August 2007
Location: Russia, Moscow rgn.
|
Experienced Contributor |
|
|
I develop some app for both Windows and FreeBSD systems. Last code changes revealed very untrivial (from my point of view) behaviour in POSIX systems. When compiled and linked, application is executed in Windows flawlessly without any runtime errors. In FreeBSD the same application causes segmentation fault on startup.
I dag into the source of this fault.
So the fault happens when static EditString class member is appeared.
It looks like this:
//.h
class AAA {static EditString es;};
//.cpp
//...
EditString AAA::es;
Debugger shows call stack when this fault happens:
| Quote: |
XInternAtom () from /usr/local/lib/libX11.so.6
Upp::XAtom ()
Upp::Ctrl::IsCompositedGui ()
Upp::Ctrl::Ctrl ()
Upp::EditField::EditField ()
Upp::EditValue<Upp::WString, Upp::ConvertString>::EditValue ()
Upp::EditString::EditString ()
|
If I make this EditString non-static, application runs flawlessly without faults. It seems like something in EditString ctor causes big segmentation fault when executed on program start, in the globals initialization period.
[Updated on: Wed, 01 April 2009 23:23] Report message to a moderator |
|
|
|
Current Time: Sun May 10 06:12:54 GMT+2 2026
Total time taken to generate the page: 0.00576 seconds
|
U++ framework
Search
Help
Members
Register
Login
Home
