Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIGSEGV on compile #14

Open
nicholasbarger opened this issue May 4, 2015 · 3 comments
Open

SIGSEGV on compile #14

nicholasbarger opened this issue May 4, 2015 · 3 comments

Comments

@nicholasbarger
Copy link

This is my first time looking into buildpack's for heroku, but I've got a .NET Mono app attempting to compile and fails with the following log (below). Is there anyway to tell which library is failing or if it is a nugget issue first that is causing the library to fail (as a dependency)?

-----> Fetching custom git buildpack... done
-----> ASP.NET app detected
-----> Downloading http://s3.amazonaws.com/mono-dependencies/cedar-14/mono-3.10.0.tar.gz
-----> Compiling Mono application
Stacktrace:
Native stacktrace:
mono() [0x4b85c8]
mono() [0x510633]
mono() [0x423bc2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f44d7424340]
[0x7f44d08dae90]
Debug info from gdb:

Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.

/tmp/buildpack_ec3381ed6f3c294e0f8f9480abcd1835/bin/compile: line 67: 242 Aborted mono ${NUGET_EXECUTABLE_PATH} restore -NonInteractive
! Push rejected, failed to compile ASP.NET app

@nicholasbarger
Copy link
Author

Well, I've done a couple things so far... I moved the heroku repo and associated heroku web role to just the MVC web app and not at the root where I had a SLN file and several class libraries as well. I committed nuget.exe into the root of the directory and began removing any potentially unused packages.

I get a new message which looks a bit further along, but still error out:

-----> Fetching custom git buildpack... done
-----> ASP.NET app detected
-----> Downloading http://s3.amazonaws.com/mono-dependencies/cedar-14/mono-3.10.0.tar.gz
-----> Compiling Mono application
Installing 'NUnit 2.6.4'.
Installing 'bootstrap 3.3.4'.
Installing 'Newtonsoft.Json 6.0.8'.
Installing 'AutoMapper 3.3.1'.
Installing 'Microsoft.AspNet.WebPages 3.2.3'.
Installing 'Microsoft.Web.Infrastructure 1.0.0.0'.
Installing 'Microsoft.AspNet.Mvc 5.2.3'.
Installing 'Microsoft.AspNet.Razor 3.2.3'.
Installing 'jQuery 2.1.3'.
Stacktrace:
Native stacktrace:
mono() [0x4b85c8]
mono() [0x510633]
mono() [0x423bc2]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f486c10e340]
mono() [0x5fbcc7]
mono() [0x5fabe9]
mono() [0x5eeefd]
mono() [0x5da6ad]
mono() [0x5ee79f]
mono() [0x5ce8c1]
mono() [0x5d64a6]
mono() [0x5d7069]
mono() [0x5f3282]
mono() [0x5f3363]
mono(mono_object_new_alloc_specific+0x21) [0x5af951]
mono(mono_object_new_specific+0x70) [0x5afa40]
mono(mono_exception_from_name_domain+0x35) [0x536855]
mono() [0x4b7ef2]
mono() [0x50ea69]
/tmp/build_a081664f6be0cb34084453aa5d2cb394/mono/lib/mono/4.5/mscorlib.dll.so(+0x12ddb2) [0x7f4863e99db2]
Debug info from gdb:

Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.

/tmp/buildpack_a081664f6be0cb34084453aa5d2cb394/bin/compile: line 67: 244 Aborted mono ${NUGET_EXECUTABLE_PATH} restore -NonInteractive
! Push rejected, failed to compile ASP.NET app

@friism
Copy link
Owner

friism commented May 4, 2015

sorry - I'm not really working on this buildpack at the moment, if anything I'm focusing on the new ASP.NET 5 stuff

@nicholasbarger
Copy link
Author

Bummer. I thought this was very exciting and brought more .NET developers further into more diverse cloud offerings and polyglot architectural decisions. Do you know if any of the other original contributors will be working on this since it's listed as the unofficial-official third party buildpack? https://devcenter.heroku.com/articles/third-party-buildpacks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants