[Mono-dev] Profiler Loading Issues
Alex Rønne Petersen
alex at alexrp.com
Mon Nov 2 08:13:27 UTC 2015
IIRC we just use dlopen(3) to load the profiler. So as far as Mono is
concerned, the best you'll get is the dlerror(3) output. You might be
able to get more detailed information with tools like strace(1),
file(1), etc, though.
On Mon, Nov 2, 2015 at 8:13 AM, Greg Young <gregoryyoung1 at gmail.com> wrote:
> Just in general. As an example if someone copies over a 64 bit build
> for a 32 bit installation.
> Or if someone has copied files into a bad location. Or if a profiler
> is just not being loaded for some unknown reason.
> Crashes have been pretty easy to debug so far.
> On Mon, Nov 2, 2015 at 7:51 AM, Alex Rønne Petersen <alex at alexrp.com> wrote:
>> Can you be a bit more specific about the issue? Is it a crash or something else?
>> On Sun, Nov 1, 2015 at 12:41 PM, Greg Young <gregoryyoung1 at gmail.com> wrote:
>>> Is there any good way of debugging profiler loading issues?
>>> Studying for the Turing test
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
> Studying for the Turing test
More information about the Mono-devel-list