Hi,
I've installed 2.0.0.4 today and with this version one of the libraries that compiled OK with 2.0.0.2 fails, but there's no error in the error view and the output window also contains no information.
Is there a compiler switch to increase the verbosity? Or any hint what could be wrong?
Mathias
2.0.0.4: Build fails without error
2.0.0.4: Build fails without error
Hi Mathias,
maybe there is an exception in the compiler. I don't know how to make this visible in Visual Studio.
Wolfgang
maybe there is an exception in the compiler. I don't know how to make this visible in Visual Studio.
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
2.0.0.4: Build fails without error
Same here.
Build fales on all my Projects having any 3rd party libraries (like DevExpress or NetPass).
Only simple DLLs and simple Projects compile.
George
Build fales on all my Projects having any 3rd party libraries (like DevExpress or NetPass).
Only simple DLLs and simple Projects compile.
George
-
- Posts: 774
- Joined: Wed May 17, 2017 8:50 am
- Location: Germany
2.0.0.4: Build fails without error
i have similar problems, but at least some error codes are shown.
After the Update to 2.0.0.4 i can´t compile no longer a small VO app that has references to VUlcan dlls only.
After the compilation this error is shown
Compiler has returned exit code -532462766
When i start in XIDE the app a win32Exception is thrown. the msg translated in short: no valid executable
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
System.ComponentModel.Win32Exception (0x80004005): Die angegebene ausführbare Datei ist keine gültige Anwendung für diese Betriebssystemplattform.
bei System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
bei System.Diagnostics.Process.Start()
bei Xide.PyrgasIdeAction.Run()
bei Xide.PyrgasIde.DoMenuAction(Object eAction, IdeMenuItem oItem)
bei Xide.PyrgasIde.ToolStripButtonClicked(Object o, EventArgs e)
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
....
After the Update to 2.0.0.4 i can´t compile no longer a small VO app that has references to VUlcan dlls only.
After the compilation this error is shown
Compiler has returned exit code -532462766
When i start in XIDE the app a win32Exception is thrown. the msg translated in short: no valid executable
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
System.ComponentModel.Win32Exception (0x80004005): Die angegebene ausführbare Datei ist keine gültige Anwendung für diese Betriebssystemplattform.
bei System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
bei System.Diagnostics.Process.Start()
bei Xide.PyrgasIdeAction.Run()
bei Xide.PyrgasIde.DoMenuAction(Object eAction, IdeMenuItem oItem)
bei Xide.PyrgasIde.ToolStripButtonClicked(Object o, EventArgs e)
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
....
2.0.0.4: Build fails without error
Mathias,
In VS you can goto Tools/Options/Projects and Solutions, Build and Run and set the verbosity to diagnostic or debug.
There is also a compiler command line option /verbose that will produce some extra info. On the Project Properties/Build tab you can add that as additional commandline option. I have no idea if that helps.
Finally, sometimes you will get more info if you disabled the shared compiler (Project Properties / Build tab)
Robert
In VS you can goto Tools/Options/Projects and Solutions, Build and Run and set the verbosity to diagnostic or debug.
There is also a compiler command line option /verbose that will produce some extra info. On the Project Properties/Build tab you can add that as additional commandline option. I have no idea if that helps.
Finally, sometimes you will get more info if you disabled the shared compiler (Project Properties / Build tab)
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
The Netherlands
robert@xsharp.eu
2.0.0.4: Build fails without error
Hi Robert,
/verbose in the project settings did not change the output (neither did switching off shared compiler), but after changing the build and run settings as you advised I get this exception in the output window.
Mathias
/verbose in the project settings did not change the output (neither did switching off shared compiler), but after changing the build and run settings as you advised I get this exception in the output window.
Mathias
Code: Select all
Unhandled Exception: System.AggregateException: One or more errors occurred. ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
8> Parameter name: index
8> at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
8> at System.Collections.Generic.List`1.get_Item(Int32 index)
8> at LanguageService.CodeAnalysis.XSharp.Syntax.InternalSyntax.XSharpPreprocessor.addDefine(IList`1 line)
8> at LanguageService.CodeAnalysis.XSharp.Syntax.InternalSyntax.XSharpPreprocessor.doDefineDirective(IList`1 original)
8> at LanguageService.CodeAnalysis.XSharp.Syntax.InternalSyntax.XSharpPreprocessor.ProcessLine(IList`1 line)
8> at LanguageService.CodeAnalysis.XSharp.Syntax.InternalSyntax.XSharpPreprocessor.PreProcess()
8> at LanguageService.CodeAnalysis.XSharp.Syntax.InternalSyntax.XSharpLanguageParser.ParseCompilationUnitCore()
8> at LanguageService.CodeAnalysis.XSharp.Syntax.InternalSyntax.XSharpLanguageParser.ParseWithStackGuard[TNode](Func`1 parseFunc, Func`1 createEmptyNodeFunc)
8> at LanguageService.CodeAnalysis.XSharp.Syntax.InternalSyntax.XSharpLanguageParser.ParseCompilationUnit()
8> at LanguageService.CodeAnalysis.XSharp.XSharpSyntaxTree.ParseText(SourceText text, XSharpParseOptions options, String path, CancellationToken cancellationToken)
8> at LanguageService.CodeAnalysis.XSharp.SyntaxFactory.ParseSyntaxTree(SourceText text, ParseOptions options, String path, CancellationToken cancellationToken)
8> at LanguageService.CodeAnalysis.XSharp.XSharpCompiler.ParseFile(XSharpParseOptions parseOptions, XSharpParseOptions scriptParseOptions, SourceText content, CommandLineSourceFile file)
8> at LanguageService.CodeAnalysis.XSharp.XSharpCompiler.ParseFile(XSharpParseOptions parseOptions, XSharpParseOptions scriptParseOptions, Boolean& addedDiagnostics, CommandLineSourceFile file, DiagnosticBag diagnostics, String& normalizedFilePath)
8> at LanguageService.CodeAnalysis.XSharp.XSharpCompiler.<>c__DisplayClass8_0.<CreateCompilation>b__0(Int32 i)
8> at Roslyn.Utilities.UICultureUtilities.<>c__DisplayClass6_0`1.<WithCurrentUICulture>b__0(T param)
8> at System.Threading.Tasks.Parallel.<>c__DisplayClass17_0`1.<ForWorker>b__1()
8> at System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)
8> at System.Threading.Tasks.Task.<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(Object )
8> --- End of inner exception stack trace ---
8> at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
8> at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
8> at System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Func`4 bodyWithLocal, Func`1 localInit, Action`1 localFinally)
8> at System.Threading.Tasks.Parallel.For(Int32 fromInclusive, Int32 toExclusive, Action`1 body)
8> at LanguageService.CodeAnalysis.XSharp.XSharpCompiler.CreateCompilation(TextWriter consoleOutput, TouchedFileLogger touchedFilesLogger, ErrorLogger errorLogger)
8> at LanguageService.CodeAnalysis.CommonCompiler.RunCore(TextWriter consoleOutput, ErrorLogger errorLogger, CancellationToken cancellationToken)
8> at LanguageService.CodeAnalysis.CommonCompiler.Run(TextWriter consoleOutput, CancellationToken cancellationToken)
8> at LanguageService.CodeAnalysis.XSharp.CommandLine.Xsc.<>c__DisplayClass2_0.<Run>b__0(TextWriter tw) in C:XSharpDevXSharpsrcCompilerxscXsc.cs:line 58
8> at LanguageService.CodeAnalysis.CommandLine.ConsoleUtil.RunWithUtf8Output[T](Func`2 func) in C:XSharpDevRoslynsrcCompilersCoreCommandLineConsoleUtil.cs:line 26
8> at LanguageService.CodeAnalysis.CommandLine.ConsoleUtil.RunWithUtf8Output[T](Boolean utf8Output, TextWriter textWriter, Func`2 func) in C:XSharpDevRoslynsrcCompilersCoreCommandLineConsoleUtil.cs:line 51
8> at LanguageService.CodeAnalysis.XSharp.CommandLine.Xsc.Run(String[] args, BuildPaths buildPaths, TextWriter textWriter, IAnalyzerAssemblyLoader analyzerLoader) in C:XSharpDevXSharpsrcCompilerxscXsc.cs:line 58
8> at LanguageService.CodeAnalysis.CommandLine.DesktopBuildClient.RunLocalCompilation(String[] arguments, BuildPaths buildPaths, TextWriter textWriter) in C:XSharpDevRoslynsrcCompilersSharedDesktopBuildClient.cs:line 66
8> at LanguageService.CodeAnalysis.CommandLine.BuildClient.RunCompilation(IEnumerable`1 originalArguments, BuildPaths buildPaths, TextWriter textWriter) in C:XSharpDevRoslynsrcCompilersSharedBuildClient.cs:line 93
8> at LanguageService.CodeAnalysis.CommandLine.DesktopBuildClient.Run(IEnumerable`1 arguments, IEnumerable`1 extraArguments, RequestLanguage language, CompileFunc compileFunc, IAnalyzerAssemblyLoader analyzerAssemblyLoader) in C:XSharpDevRoslynsrcCompilersSharedDesktopBuildClient.cs:line 49
8> at LanguageService.CodeAnalysis.XSharp.CommandLine.Program.Main(String[] args, String[] extraArgs) in C:XSharpDevXSharpsrcCompilerxscProgram.cs:line 35
8> at LanguageService.CodeAnalysis.XSharp.CommandLine.Program.Main(String[] args) in C:XSharpDevXSharpsrcCompilerxscProgram.cs:line 31
2.0.0.4: Build fails without error
Mathias,
Can you zip your solution and mail it to me ?
Or create a ticket and attach the solution ?
Robert
Can you zip your solution and mail it to me ?
Or create a ticket and attach the solution ?
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
The Netherlands
robert@xsharp.eu
2.0.0.4: Build fails without error
Robert,
I'm really sorry, but at least atm I am not allowed to give you the code.
If I can do anything else, like test with a compiler version that does more logging, please let me know.
Mathias
I'm really sorry, but at least atm I am not allowed to give you the code.
If I can do anything else, like test with a compiler version that does more logging, please let me know.
Mathias
2.0.0.4: Build fails without error
Hello,
this must be a problem of the public build.
With my FoX version of the compiler all my applications build and run as before.
Wolfgang
this must be a problem of the public build.
With my FoX version of the compiler all my applications build and run as before.
Wolfgang
Wolfgang Riedmann
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
Meran, South Tyrol, Italy
wolfgang@riedmann.it
https://www.riedmann.it - https://docs.xsharp.it
2.0.0.4: Build fails without error
Same here - no prob with Foxbuild
Karl
Karl
Regards
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)
Karl
(on Win8.1/64, Xide32 2.20, X#2.20.0.3)