You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The atexit imlementation of the KLEE-libc does not work, when exit is called "explicitely".
Note that at an explicit exit call, the functions registered with atexit ought to be called.
So, the following CHECK does fail when running with the KLEE libc (but it works fine with uclibc). fwc@aebd8f83 shows the complete test.
The bug occurs since the functions registered via atexit are called by RunAtExit which is marked with __attribute__((destructur)). The destructor is called after exiting main. The "explicit" exit-call is handled by the SpecialFunctionHandler, which directly terminates the state, which thus does not exit main, thus not calling the destructor.
The text was updated successfully, but these errors were encountered:
The
atexit
imlementation of the KLEE-libc does not work, whenexit
is called "explicitely".Note that at an explicit
exit
call, the functions registered withatexit
ought to be called.So, the following
CHECK
does fail when running with the KLEE libc (but it works fine with uclibc).fwc@aebd8f83 shows the complete test.
The bug occurs since the functions registered via
atexit
are called byRunAtExit
which is marked with__attribute__((destructur))
. The destructor is called after exitingmain
. The "explicit"exit
-call is handled by theSpecialFunctionHandler
, which directly terminates the state, which thus does not exitmain
, thus not calling the destructor.The text was updated successfully, but these errors were encountered: