roman-yagodin/csexec

Command-line tool to run C# source files as scripts on Linux with Mono

csexec's Issues

Check for bashisms and convert to /bin/sh

Cannot run csexec scripts with no compiler args

Need to test running csexec scripts with no compiler args from command line. It seem like csexec currently expect some compiler args.

Unpredictable behavior with long paths

Attempt to run script or compiled binary using paths longer than ~155 chars (actual value differs from case to case) will lead to unexpected results, which are somewhat random:

1. Segfault (more frequently):

* Assertion at strenc.c:183, condition `utf8!=NULL' not met

Stacktrace:

  at <unknown> <0xffffffff>
  at (wrapper managed-to-native) System.IO.MonoIO.GetFileStat (string,System.IO.MonoIOStat&,System.IO.MonoIOError&) <0x0005d>
  at System.IO.File.FillAttributeInfo (string,System.IO.MonoIOStat&,bool,bool) <0x00040>
  at System.IO.FileSystemInfo.Refresh () <0x00024>
  at System.IO.DirectoryInfo.get_Exists () <0x0001b>
  at System.IO.Directory.CreateDirectoriesInternal (string) <0x000b9>
  at System.IO.Directory.CreateDirectory (string) <0x000a0>
  at R7.Scripting.Log..ctor (string,bool) <0x0004b>
  at R7.Scripting.Script..ctor (string[]) <0x0007f>
  at R7.Scripting.DesktopScript..ctor (string[]) <0x00017>
  at MyScript..ctor (string[]) <0x00017>
  at Program.Main (string[]) <0x00033>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <0x000f5>
...

2. No segfault, but Main process quickly grows in memory to about 4 Gb - less frequently, but very annoying!

The problem seems of Mono/.NET origin, but it would be nice to overcome this to ensure scripts can run from any directory as a working directory, or at least block their execution in a nice way.