Hi,
This is a JIT problem, it will be hard to track down without a testcase.
You can try changing this line in mono/utils/mono-codeman.c:
#define BIND_ROOM 8
to
#define BIND_ROOM 4
It might fix the issue.
Zoltan
On Tue, Aug 13, 2013 at 7:44 AM, Bassam Tabbara
Unfortunately that did not help. Still seeing the problem. I'm still working on
a test case but I'm not having much luck so far in getting an isolated repro.
I was able to get a debugger attached to the process right when handle_thunk
asserts, and there were 6 threads with the following call
Hi,
Can you see whats at 'code' and 'target' at frame #3, i.e.
x/10i code
x/10i target
Zoltan
On Wed, Aug 14, 2013 at 1:48 AM, Bassam Tabbara bas...@symform.com wrote:
Unfortunately that did not help. Still seeing the problem. I'm still
working on a test case but I'm not having much
I meant frame #2, i.e.
#2 0x00172ca8 in arm_patch
Zoltan
On Wed, Aug 14, 2013 at 2:14 AM, Zoltan Varga var...@gmail.com wrote:
Hi,
Can you see whats at 'code' and 'target' at frame #3, i.e.
x/10i code
x/10i target
Zoltan
On Wed, Aug 14, 2013 at 1:48 AM, Bassam Tabbara
I've written a small patch that causes 'Locked' files on Mac to be
correctly reported as having FILE_ATTRIBUTE_READONLY set:
https://github.com/richard-fine/mono/commit/8ea7501dd7aec2ae9f55955cedf3a39df07762e9
I think it's the correct way to handle that flag. It's not
POSIX-compliant and
