Everything's in the title, if I try to dotnet run it exits with no message, however using dotnet exec on the DLL outputs "segmentation fault" and exits.
4
-
Which debian version you have? Also, have you tried it in debug mode on debian to see if any message is shown with dotnet run?Gusman– Gusman2017-06-15 20:05:34 +00:00Commented Jun 15, 2017 at 20:05
-
2Also, the exec function is not supposed to be called directly by the user, look at the last entry on this issue: github.com/dotnet/cli/issues/2243Gusman– Gusman2017-06-15 20:08:18 +00:00Commented Jun 15, 2017 at 20:08
-
Linux aam-srv 4.5.7-std-3 #1 SMP Tue Jul 12 09:56:30 UTC 2016 x86_64 GNU/LinuxErlite– Erlite2017-06-15 20:18:41 +00:00Commented Jun 15, 2017 at 20:18
-
dotnet run quits anywayErlite– Erlite2017-06-15 20:19:06 +00:00Commented Jun 15, 2017 at 20:19
Add a comment
|
1 Answer
Okay, so another developer working on the project found the problem. I caused a stack overflow (how convenient) on one of the custom attributes I made. Here's the code:
private string Message
{
get
{
return this.Message;
}
set
{
this.Message = value;
}
}
So basically, it was calling itself indefinitely. What I was supposed to do instead was create a second string to access it from:
private string Message
{
get
{
return this.message;
}
set
{
this.message = value;
}
}
private string message;
Hope it helps some of you!