lucasg/Dependencies · error

Modules backtrace:

Error message

Modules backtrace:

What it means

Header line printed by SafeExecutor<T>'s catch(Exception ex) just before re-throwing the newly-wrapped RethrownException (Program.cs:553). It signals that the subsequent ` - "<path>"` lines (error 2) form a module backtrace from the root down to the failing node. Diagnostic only.

Source

Thrown at Dependencies/Program.cs:553

            SafeExecutor(() => { action(); return 0; });
        }

        private T SafeExecutor<T>(Func<T> action)
        {
            try
            {
                return action();
            }
            catch (RethrownException rex)
            {
                Console.Error.WriteLine(" - \"{0:s}\"", Filepath);
                throw rex;
            }
            catch (Exception ex)
            {
                Console.Error.WriteLine("[!] Unhandled exception occured while processing \"{1:s}\"", RecursionLevel, Filepath);
                Console.Error.WriteLine("Stacktrace:\n{0:s}\n", ex.StackTrace);
                Console.Error.WriteLine("Modules backtrace:");
                throw new RethrownException(ex);
            }
            finally
            {
                //
                
            }

            // return default(T);
        }

        // Json exportable
		public string ModuleName;
        public string Filepath;
        public ModuleSearchStrategy SearchStrategy;
        public List<PeDependencyItem> Dependencies
        {
            

View on GitHub (pinned to 1997a40000)

Solutions

1. Read the ` - "<path>"` lines printed after this header bottom-up to reconstruct which dependency chain led to the failure.
2. Address the root-cause exception identified via the Stacktrace (error 4); the backtrace only shows propagation, not the cause.

try { Program.DumpDependencyChain(pe, Program.PrettyPrinter, depth); }
catch (RethrownException)
{
    // Module backtrace was already printed to stderr; nothing further to parse here.
}

When it happens

Trigger: Immediately follows the Stacktrace line (error 4) whenever a fresh exception is wrapped into a RethrownException during dependency resolution.

Common situations: Same as errors 3-4; this line simply frames the backtrace output that follows.

Related errors

• Stacktrace: {0:s}
• [x] "Malformed" pe manifest for file {0:s} : {1:s}
• [x] Exception : {0:s}
• - "{0:s}"
• [!] Unhandled exception occured while processing "{1:s}"

AI-assisted analysis of lucasg/Dependencies@1997a40000 (2026-08-13). Data as JSON: /api/errors/76f7bd52939d3dfb. Report an issue: GitHub.