Re: [Mono-list] Mono 1.1.14 and Indy.Sockets

2006-04-12 Thread matt 
On Monday 10 April 2006 14:47, Paolo Molaro wrote:
 On 04/07/06 matt wrote:
  For my project I use the Indy.Sockets opensource library that used to
  work well with mono 1.1.12 and 1.1.13.
  Now I get:
 
  Invalid IL code in Indy.Sockets.Thread:.ctor (bool,bool,string): IL_0017:
  stloc.0

 This should be fixed in svn.
 Thanks for the report.

 lupus


Wow!  I thought it would be an obscure and complicated problem about which 
nobody was interested, and you come and say should be fixed
Impressive :-)
Many thanks. I'm going to grab mono from SVN and test it.

Matt


PS:sorry fo having polluted an existing thread.

___
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list

Re: [Mono-list] Mono 1.1.14 and Indy.Sockets

2006-04-10 Thread Paolo Molaro 
On 04/07/06 matt wrote:
 For my project I use the Indy.Sockets opensource library that used to work 
 well with mono 1.1.12 and 1.1.13.
 Now I get:
 
 Invalid IL code in Indy.Sockets.Thread:.ctor (bool,bool,string): IL_0017: 
 stloc.0

This should be fixed in svn.
Thanks for the report.

lupus

-- 
-
[EMAIL PROTECTED] debian/rules
[EMAIL PROTECTED] Monkeys do it better
___
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list

[Mono-list] Mono 1.1.14 and Indy.Sockets

2006-04-07 Thread matt 
Hi All,

I just downloaded and installed Mono 1.1.14 with Suse 10.0 RPMs.

For my project I use the Indy.Sockets opensource library that used to work 
well with mono 1.1.12 and 1.1.13.
Now I get:

Invalid IL code in Indy.Sockets.Thread:.ctor (bool,bool,string): IL_0017: 
stloc.0
in 0x0 unknown method
in 0x00010 Indy.Sockets.TIdStringsFCL:set_NameValueSeparator (Char AValue)
in 0x0001f Indy.Sockets.TIdStringsFCL:GetNameValueSeparator ()
in 0xd Indy.Sockets.TIdStringsFCL:get_NameValueSeparator ()
in 0x0006c Indy.Sockets.TIdStringsFCL:IndexOfName (System.String AName)
in 0x0001f Indy.Sockets.TIdStringsFCL:GetValue (System.String AName)
in 0x00010 Indy.Sockets.TIdStringsFCL:get_Values (System.String AName)
in 0x00339 Indy.Sockets.MessageDecoderMIME:ReadHeader ()
in 0x00267 Indy.Sockets.MessageClient:ReceiveBody (Indy.Sockets.Message 
AMsg, System.String ADelim)
in 0x000a0 Indy.Sockets.POP3:Retrieve (Int32 MsgNum, Indy.Sockets.Message 
AMsg)
in (wrapper remoting-invoke-with-check) Indy.Sockets.POP3:Retrieve 
(int,Indy.Sockets.Message)
in [0x00084] 
(at /home/m/dev/shM/Protocols/EventsReceivers/POP3MailboxChecker.cs:49) 
shMonitor.Core.Protocols.POP3MailboxChecker:Check ()
in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()


I am using Indy.Sockets 10.1.5 (actual stable version). The error seems to be 
related to the POP3 class of Indy.Sockets (which checks mails in a POP3 
mailbox).
Do these errors really show a problem with Indy.sockets or are they due to new 
Mono version?
 
My config:
 # uname -a
Linux linux 2.6.15-default #3 SMP Fri Jan 13 19:09:35 CET 2006 i686 i686 i386 
GNU/Linux

#mono -V
Mono JIT compiler version 1.1.14, (C) 2002-2005 Novell, Inc and Contributors. 
www.mono-project.com
TLS:   normal
GC:Included Boehm (with typed GC)
SIGSEGV:   normal
Disabled:  none

Sorry if my problem is only indy-related.

Regards,

Matt






On Friday 07 April 2006 15:11, Bradley, Peter wrote:
 Has Mono lost a user?  If so, do we know why?  This is a very busy site.

 From netcraft:

 20-Mar-2006:

 Laterooms Ltd
 http://toolbar.netcraft.com/netblock?q=LATEROOMS,194.24.250.0,194.24.25
 1.255 194.24.250.200Windows Server 2003 Microsoft-IIS/6.0



 5-Mar-2006:

 Laterooms Ltd
 http://toolbar.netcraft.com/netblock?q=LATEROOMS,194.24.250.0,194.24.25
 1.255 194.24.250.200 unknown Apache/1.3.33 Debian GNU/Linux
 mod_mono/1.1.13 mod_gzip/1.3.26.1a PHP/4.3.10-16 mod_ssl/2.8.22
 OpenSSL/0.9.7e



 Interestingly, just recently the site has become a lot less stable.  It
 often fails with a .NET untrapped exception, Server too busy.



 Perhaps some sales suit from Novell ought to pay them a visit.
 Hopefully whilst they still have a problem.



 Cheers





 Peter

___
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list