CODEWITHSUNDEEP
linuxcudanvidiansight
Steinin
Steinin

Reputation: 541

NSight Profiler Signal 139

I am trying to profile my program using the inbuilt profiler in NSight but the profiling session terminates immediately after starting and I receive as feedback "Warning: Application received signal 139". What does this mean?

I also receive the following error message:

Unable to read the entire session timeline. The displayed timeline may be empty or incomplete because the application aborted or failed to flush profile data before exiting. The application should call cudaDeviceReset() before exiting to ensure that all profile data is flushed.

Upvotes: 2

Views: 3974

Answers (3)

Alexander
Alexander

Reputation: 11

Checking Start application with profiling enabled fixed it for me. It is on by default, but I wanted explicit control so turned it off initially. Disabling concurrent kernel profiling worked too, but it prevents you from profiling apps with dynamic parallelism.

Upvotes: 1

David
David

Reputation: 46

In nsight, go to Profile Configurations and then the Profiler tab. Uncheck "Enable concurrent kernel profiling".

Upvotes: 2

Xuan Wang
Xuan Wang

Reputation: 71

Does you program require some command line parameters? The debugger and profiler may haven't correctly pick your CLI options from your configuration. You need the specify them in Nsight User Property, or Activity page for profiler.

Upvotes: 0

Related Questions