Hi list,

I am sorry I didn't find an ECL-User mailing list, so I post this question here. If here is not the right place to ask this kind of question, please let me know.

I wrote a simple GTK program using cl-gtk2-gtk, please see it here:
http://depot.kdr2.com/scrappy/202001/ecl-gtk.lisp

After I installed the dependent packages using quicklisp,  I ran it with `ecl --load ecl-gtk.lisp`, then, ECL started to compile files. It compiled for about 5 hours, and emitted an error, here is the log:
http://depot.kdr2.com/scrappy/202001/ecl-gtk.log

Then I run it again, it gave a different error:

```
$ ecl --load ecl-gtk.lisp
;;; Loading "/home/kdr2/Work/mine/DS-III/explore/common-lisp/ecl-gtk.lisp"
;;; Loading "/home/kdr2/quicklisp/setup.lisp"
;;; Loading #P"/usr/lib/x86_64-linux-gnu/ecl-16.1.3/asdf.fas"
An error occurred during initialization:
The slot ASDF/PLAN::STAMP in the object #<action-status

Condition of type: STACK-OVERFLOW
BINDING-STACK overflow at size 10240. Stack can probably be resized.
Proceed with caution.
Available restarts:

1. (CONTINUE) Extend stack size
2. (RETRY) Retry ASDF operation.
3. (CLEAR-CONFIGURATION-AND-RETRY) Retry ASDF operation after resetting the configuration.
4. (RETRY) Retry completing compilation for #<package-inferred-system "asdf">.
5. (ACCEPT) Continue, treating completing compilation for #<package-inferred-system "asdf"> as having been successful.
6. (RETRY) Retry ASDF operation.
7. (CLEAR-CONFIGURATION-AND-RETRY) Retry ASDF operation after resetting the configuration.
8. (CONTINUE) Ignore initialization errors and continue.
9. (ABORT) Quit ECL unsafely, ignoring all existing threads.

Top level in: #<process TOP-LEVEL>.
>

```

Here is the information of my system:

# System Summary Report ##############################
        Date | 2020-01-04 12:57:44 UTC (local TZ: CST +0800)
    Hostname | Debian-X230
      Uptime | 45 days,  4:37, 12 users,  load average: 0.16, 0.04, 0.01
     Release | Debian GNU/Linux bullseye/sid (sid)
      Kernel | 4.18.0-1-amd64
Architecture | CPU = 64-bit, OS = 64-bit
   Threading | NPTL 2.29
     SELinux | No SELinux detected
# Processor ##################################################
  Processors | physical = 1, cores = 2, virtual = 4, hyperthreading = yes
      Speeds | 1x1546.829, 1x1599.499, 1x1608.905, 1x1643.428
      Models | 4xIntel(R) Core(TM) i7-3520M CPU @ 2.90GHz
      Caches | 4x4096 KB
# Memory #####################################################
       Total | 15.40G
        Free | 6.30G
        Used | physical = 3.32G, swap = 902.84M, virtual = 4.20G
     Buffers | 5.78G
      Caches | 11.51G
        Used | 1.59G
  Swappiness | vm.swappiness = 60
 DirtyPolicy | vm.dirty_ratio = 40, vm.dirty_background_ratio = 10
 DirtyStatus | vm.dirty_bytes = 0, vm.dirty_background_bytes = 0


$ ecl --version
ECL 16.1.3
$ gcc --version
gcc (Debian 9.2.1-17) 9.2.1 20191102
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.



Anyone knows why and how to fix this?

Thanks!

Greetings.

ZHUO Qingliang (KDr2, http://kdr2.com)