B
byoung2735
Guest
We are receiving a Memory Violation running a very large ABL procedure. This procedure is doing a read of a temporary table. I can't reproduce it so far in a simple case, but was wondering if anyone had seen/dealt with it before. This is the final line in the protrace stack - #28 [0x7d21ed5d] __tls_get_addr@@GLIBC_2.3+0x7d21ed5d from /lib64/libc.so.6 Thanks.
Continue reading...
Continue reading...