Re: GC issue in mono 0.31

Hello Hans,

I've now tried some more things:

* Upgrading to binutils 2.13.90 didn't change anything;

* Running kernel 2.4.20 didn't essentially change anything
  either;
  
* gctest from full 6.2 gc version does not seem to succeed:

Switched to incremental mode
Emulating dirty bits with mprotect/signals
Killed

It failes when linked statically as well. Exception happens
not at that same place as when linked from mono, but I don't
know exactly where at this time (Old gdb refused to work with
new gcc and/or binutils, I'm thinking how to better solve this)

Please let me know if I should do some other tests or if you
need more details/outputs/etc.
-- 
Best regards,
 Nikolai Zhubr
 
Wednesday, 05 May, 2004, 1:34:34, you wrote:

> I assume nothing is prelinked?  I don't think that was even an option
> on RedHat 7.1.

> It would be helpful to set a breakpoint in GC_add_roots_inner, and
> verify that it's actually being called with (DATAEND, which is
> defined to be) _end as its middle argument.

> It looks like both mono and libmono define _end.  By the normal ELF
> default symbol lookup rules, I believe libmono references to _end should see the
> definition in the main program.  If this is indeed not happening, and if the
> libmono developers aren't aware of other relevant issues, I would ask
> on a binutils mailing list for ideas.

> Hans

>> -----Original Message-----
>> From: Nikolai Zhubr [mailto:[email protected]]
>> Sent: Tuesday, May 04, 2004 12:53 PM
>> To: Boehm, Hans
>> Cc: [email protected]; [email protected]
>> Subject: Re: GC issue in mono 0.31
>> 


_______________________________________________
Mono-gc-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-gc-list