The following program will result in a segmentation fault when the two marked lines are uncommented

шифр 419900зс5^
еев1а3
*name gost-10859
*assembler
*bemsh
inp$$$
main start 1
 vtm '30000'(13)
 *66 is
 atx '10'(8)
* *66 is        <--- uncomment to 
* atx '10'(8)  <--- cause a crash
printo extrd printo
 vtm res(14)
 its 14
 vtm res+len-1(14)
 its 14
 vtm N(14)
 its 14
 vtm M(14)
 its 14
 vjm printo(13)
 *74
N dc b'30'
M dc b'2'
is atx start
 atx fin-1
 atx
 atx res
 dc b'-1'
rep equ 2
start nop
 dc (rep)b'7'
 dc (rep)b'1'
 dc (rep)b'5'
 dc (rep)b'12'
 dc (rep)b'6'
 dc (rep)b'10'
 dc (rep)b'3'
 dc (rep)b'4'
 dc (rep)b'2'
 dc (rep)b'11'
fin nop
len equ fin-start
res dc (len)b'0'
 fin
eoi$$$
trn$$$
0-0
end$$$
*main main
*execute
*end file
<6 ` characters>
еконец 

besmtool dump terminates its copy loop when it encounters a nonexistent zone. There are 2 issues with that:

1. It does so silently, giving the user the idea that everything is a-ok (unless the user cares to check and see that too few zones have been copied). A more prominent warning/error message should be in order.
2. There needs to be at least an option to proceed with the copying and supply a blank page (разметочный код) for the missing zone contents. Otherwise, dumping a sparse disk becomes a really tedious exercise.

The following program produces (using standard program 4) a nicely formatted code printout by default, and a corrupted one with -x

шифр 419900зс5^
еев1а3
*name gost-10859
*assembler
*no list
*no load list
 program: ,name,
 13,vtm,4096
 ,*66,adr
 , ,4
 ,*74,
 a1:,xta,a
 ,a/x,b
 ,a*x,c
 ,arx,=1
 adr:, ,a1
 , ,a1+2
 a:,real,5.0
 b:,real,6.0
 c:,real,-7.0
  ,end ,
*execute
*end file
<6 ` characters>
еконец

The build process is bitching about not being able to find aclocal-1.11, because my aclocal is 1.13.
I am seeing, that aclocal-1.11 (the version part) is [semi]hardcoded in aclocal.m4.
Is this the intention and how can I straighten this out?

besmtool list's idea of what is a disk file is too restrictive compared to that of the emulator.
It is sufficient to
echo -n DISK > 1234
for the emulator to view 1234 as a valid disk, while besmtool wouldn't recognize it as such.

На одной из Linux машин вылезла интересная вещь.
После запуска ./configure --prefix=некоторый_путь, а затем сборки make проходит компиляция и скачивание дисков.
Также успешно генерируются диски, но почему-то не всегда переносятся в этот --prefix по команде make install в итоге dispak работает, но выдает ошибку переполнения АУ.
Помог запуск его с помощью strace для определения путей и подсовыванием дисков в $HOME/.besm6/
Может этот способ починки еще кому-то поможет.