Groups | Search | Server Info | Login | Register

Groups > comp.lang.tcl > #55542

Re: Very hard to debug issue

Show all headers | View raw

Am 06.03.2026 um 15:51 schrieb Rich:
> Which is the part that very much points to/something/ specific to that
> one machine.  Either path names with spaces or utf-8 characters that
> are not handled correctly all the way through, or PATH= setting
> differences.
Yes, I know.
This is why I initially suspected that it the Firewall or the Antivirus.

I got some logs from the user and it looks like the issue is in this 
command below which is initializing the threads.

thread::create -preserved "namespace eval ::meshparts {} {variable 
sourceexe $sourceexe; variable sourcedir \"$sourcedir\"; variable 
sourcefile \"$sourcefile\"}; thread::wait"

Pretty dumb error: On one place the quotes arround $sourceexe are 
missing, since sourceexe is a path which my contain empty spaces.
All other paths are enclosed between quotes.

It's amaizing, that the code worked until now, since this variable is 
central for the working of the whole app.

Could be that no other user stores the executable in a directory with 
empty spaces. Amazing!

I know I should have used "list" to build up the string, but in this 
case there are those semicolons in the string ";" and I always have 
issues combining ";" in the "list" command.

So I think this is problem solved, but I will know more on Monday.

Many thanks to all!

Cheers
Alex

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