Robin Gareus 25d1209bb4 Only dump SessionEvent pool in debug builds ... This ensures that the user will see a "POOL OUT OF MEMORY" message. In rare case dumping the pool can segfault when printing the Event, The pool is zero initialized and only ever contains events, so in theory it is safe to print them..		2022-07-07 22:34:11 +02:00
..
boost-debug
msvc
MSVCpbd
pbd
test
base_ui.cc
basename.cc
boost_debug.cc
cartesian.cc
ChangeLog
cocoa_open_uri.mm
command.cc
configuration_variable.cc
controllable.cc
convert.cc
COPYING
cpus.cc
crossthread.cc
crossthread.posix.cc
crossthread.win.cc
debug_rt_alloc.c
debug.cc
demangle.cc
enums.cc
enumwriter.cc
epa.cc
error.cc
event_loop.cc
ffs.cc
file_archive.cc
file_utils.cc
fpu.cc
gettext.h
glib_event_source.cc
id.cc
libpbd.pc.in
libpbd.spec.in
locale_guard.cc
localtime_r.cc
malign.cc
md5.cc
microseconds.cc
mountpoint.cc
openuri.cc
pathexpand.cc
pbd.cc
pcg_rand.cc
pool.cc
property_list.cc
pthread_utils.cc
reallocpool.cc
receiver.cc
resource.cc
run-tests.sh
search_path.cc
semutils.cc
shortpath.cc
signals.cc
spinlock.cc
stacktrace.cc
stateful_diff_command.cc
stateful.cc
string_convert.cc
strreplace.cc
strsplit.cc
system_exec.cc
textreceiver.cc
timer.cc
timing.cc
tlsf.cc
transmitter.cc
undo.cc
uuid.cc
whitespace.cc
windows_mmcss.cc
windows_special_dirs.cc
windows_timer_utils.cc
wscript
xml++.cc