Hi Johann --
I have no problems with pdump when I try to build 21.5 tip with the address
sanitizer from clang-3.4. I do have a distinct problem (possibly in the
XEmacs Lisp runtime, possibly in my setup) when running interpreted code.
Any XEmacs work you can do is far more helpful if it’s on 21.5, no-one is
developing 21.4.
Best,
Aidan
Ar an deichiú lá de mí na Nollaig, scríobh Johann 'Myrkraverk' Oskarsson:
This is what happens when I try to build XEmacs 21.4.24 with the
address sanitizer enabled.
This is the relevant ./configure switch:
'--cflags=-std=gnu89 -g -fsanitize=address -fno-omit-frame-pointer'
Dumping under the name xemacs
=================================================================
==56900==ERROR: AddressSanitizer: global-buffer-overflow on address
0x0001008b8da8 at pc 0x000100cba91a bp 0x7fff5fbf8110 sp
0x7fff5fbf78c8
READ of size 48 at 0x0001008b8da8 thread T0
#0 0x100cba919 in __asan_memcpy
(libclang_rt.asan_osx_dynamic.dylib:x86_64+0x50919)
#1 0x10015534c in pdump_dump_data dumper.c:634
#2 0x100154cab in pdump_scan_by_alignment dumper.c:828
#3 0x100153e8a in pdump dumper.c:1060
#4 0x1000fc22d in Fdump_emacs emacs.c:3217
#5 0x100100189 in Feval eval.c:3335
#6 0x100102f17 in Fprogn eval.c:775
#7 0x1000ffa3d in Feval eval.c:3308
#8 0x100102b83 in Fif eval.c:691
#9 0x1000ffa3d in Feval eval.c:3308
#10 0x100101e6c in Feval eval.c:3414
#11 0x1005312e7 in readevalloop lread.c:1449
#12 0x10052c86b in Fload_internal lread.c:737
#13 0x1001007a6 in Feval eval.c:3335
#14 0x10010d82b in condition_case_1 eval.c:1652
#15 0x10007f7cf in top_level_1 cmdloop.c:206
#16 0x10010c69b in internal_catch eval.c:1318
#17 0x10007ebec in initial_command_loop cmdloop.c:285
#18 0x1000f2d84 in xemacs_21_4_24_i386_apple_darwin14_5_0 emacs.c:2460
#19 0x1000fa5b5 in main emacs.c:2829
#20 0x7fff8818b5c8 in start (libdyld.dylib:x86_64+0x35c8)
--
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after forty pints of stout’
(C. Moore)