singlefile apps do not emit file and line info when printing stacktraces

[am11]

dotnet/diagnostics#2192 (comment)

e.g. this code:

using System;
class Program
{
    static void Main() => throw new Exception("foo");
}

would yield:

Unhandled exception. System.Exception: foo
   at Program.Main()

instead of what we get with non-singlefile execution:

Unhandled exception. System.Exception: foo
at Program.Main() in /home/am11/projects/app1/Program.cs:line 4

cc @mikem8361

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[jkotas]

The guidance is to use embedded PDBs for this scenario. See https://docs.microsoft.com/en-us/dotnet/core/deploying/single-file#include-pdb-files-inside-the-bundle .

[am11]

I have tested with embedded PDB, it still does not print file/line info in stacktraces.

The guidance does not say that the default, DebugType=portable, for singlefile is unsupported, but rather 'PDB can be embedded'. If the default setting has no use for singlefile, should the SDK be updated to report error?

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

dotnet/diagnostics#2192 (comment)

e.g. this code:

using System;
class Program
{
    static void Main() => throw new Exception("foo");
}

would yield:

Unhandled exception. System.Exception: foo
   at Program.Main()

instead of what we get with non-singlefile execution:

Unhandled exception. System.Exception: foo
at Program.Main() in /home/am11/projects/app1/Program.cs:line 4

cc @mikem8361

Author:	am11
Assignees:	-
Labels:	area-Diagnostics-coreclr, untriaged
Milestone:	-

[mikem8361]

To support embedded PDBs for single-file the StackTraceSymbols.cs code here needs the assembly path which doesn't exist for single-file apps (see here where GetPath() returns an empty assembly path).

[jkotas]

Looks like a dup of #11261

[am11]

1. Embedded - probably duplicate of No source/line info for embedded PDBs in a "in-memory" assembly for unhandled exceptions #11261
2. Physical PDB (default single file build using .NET5 SDK) - is this unsupported?

[jkotas]

Physical PDB (default single file build using .NET5 SDK) - is this unsupported?

It is unsupported today. Embedded PDBs are the recommended way to make this work for single file.

[AdamCaviness]

I'm watching this with interest. We need stacktraces with line numbers but to achieve that at present we have to deploy 468 files due to this issue. We are using Embedded PDBs. Is there a workaround in .net5.0 where I can use the old 3.1 self-extracting single-file approach to avoid this issue? Thanks.