Groups | Search | Server Info | Login | Register

Groups > comp.lang.tcl > #55531

Re: Very hard to debug issue

From meshparts <alexandru.dadalau@meshparts.de>
Newsgroups comp.lang.tcl
Subject Re: Very hard to debug issue
Date 2026-03-05 16:43 +0100
Message-ID <10oc8b0$17vq0$1@tota-refugium.de> (permalink)
References <10o8p08$164bd$1@tota-refugium.de> <10o9amg$2tsin$1@dont-email.me> <10ob7cf$178bu$2@tota-refugium.de> <10oc0g7$3qn3a$1@dont-email.me>

Show all headers | View raw

Am 05.03.2026 um 14:29 schrieb Rich:
> How should we know?  This is the first time in this thread you've
> actually told us it does not happen in the main process.  If you want
> help, you have to provide the relevant information for us to help.
Not true!
See my original post:
"In order to provide an workarround, I changed the first step so that 
that command is executed directly in the main thread instead in a 
parallel thread. This works! "

Back to comp.lang.tcl | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 09:03 +0100
  Re: Very hard to debug issue undroidwish <undroidwish@googlemail.com> - 2026-03-04 10:12 +0100
    Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:35 +0100
    Re: Very hard to debug issue Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-03-11 17:12 +0000
  Re: Very hard to debug issue Ralf Fassel <ralfixx@gmx.de> - 2026-03-04 12:09 +0100
    Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:37 +0100
      Re: Very hard to debug issue Christian Gollwitzer <auriocus@gmx.de> - 2026-03-04 21:26 +0100
        Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 07:25 +0100
    Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:40 +0100
    Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:41 +0100
    Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-04 12:42 +0100
  Re: Very hard to debug issue Rich <rich@example.invalid> - 2026-03-04 13:05 +0000
    Re: Very hard to debug issue et99 <et99@rocketship1.me> - 2026-03-04 17:09 -0800
      Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 07:19 +0100
    Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 07:20 +0100
      Re: Very hard to debug issue Rich <rich@example.invalid> - 2026-03-05 13:29 +0000
        Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 16:43 +0100
          Re: Very hard to debug issue Rich <rich@example.invalid> - 2026-03-05 17:02 +0000
        Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-05 16:45 +0100
          Re: Very hard to debug issue et99 <et99@rocketship1.me> - 2026-03-05 11:49 -0800
            Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-06 08:32 +0100
              Re: Very hard to debug issue Rich <rich@example.invalid> - 2026-03-06 14:51 +0000
                Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-06 18:39 +0100
                Re: Very hard to debug issue Ralf Fassel <ralfixx@gmx.de> - 2026-03-16 12:12 +0100
                Re: Very hard to debug issue meshparts <alexandru.dadalau@meshparts.de> - 2026-03-18 21:28 +0100

csiph-web