List Info

Thread: Using version 0.11 on SuSE 10.1
Using version 0.11 on SuSE 10.1
user name
 2006-05-29 09:34:22 
This is problably not a real issue with remoting, but with
the auxiliary
process. In any case, try starting MD with the --ipc-tcp
option, so it
will use tcp instead of unix sockets.

El dg 28 de 05 del 2006 a les 18:19 +0200, en/na Contact va
escriure:
> Hi,
>  
> I have installed MD 0.11 on a fresh install of SuSE
10.1 and I get the
> follwoing error message upon startup:
>  
> System.Runtime.Remoting.RemotingException: Unix
transport error.
> 
> Server stack trace: 
> in <0x0008f>
Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveMessageStat
us
> (System.IO.Stream networkStream, System.Byte[] buffer)
> in <0x0017c>
>
Mono.Remoting.Channels.Unix.UnixClientTransportSink:ProcessM
essage (IMessage
> msg, ITransportHeaders requestHeaders, System.IO.Stream
requestStream,
> ITransportHeaders responseHeaders, System.IO.Stream
responseStream)
> in <0x0024c>
>
Mono.Remoting.Channels.Unix.UnixBinaryClientFormatterSink:Sy
ncProcessMessage
> (IMessage msg)
> 
> Exception rethrown at [0]: 
> ---> System.Runtime.Remoting.RemotingException:
Connection closed
> in <0x0006c>
Mono.Remoting.Channels.Unix.UnixMessageIO:StreamRead
> (System.IO.Stream networkStream, System.Byte[] buffer,
Int32 count)
> in <0x00044>
Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveMessageStat
us
> (System.IO.Stream networkStream, System.Byte[]
buffer)--- End of inner
> exception stack trace ---
> 
> in <0x0008f>
Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveMessageStat
us
> (System.IO.Stream networkStream, System.Byte[] buffer)
> in <0x0017c>
>
Mono.Remoting.Channels.Unix.UnixClientTransportSink:ProcessM
essage (IMessage
> msg, ITransportHeaders requestHeaders, System.IO.Stream
requestStream,
> ITransportHeaders responseHeaders, System.IO.Stream
responseStream)
> in <0x0024c>
>
Mono.Remoting.Channels.Unix.UnixBinaryClientFormatterSink:Sy
ncProcessMessage
> (IMessage msg)
> 
> Any idea? I'm wondering why MD needs to call into the
Remoting classes upon
> startup.
> 
> Thanks in advance.
> 

_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
Using version 0.11 on SuSE 10.1
user name
 2006-05-29 10:35:04 
Hi,

On 5/29/06, Lluis Sanchez <lluisximian.com> wrote:
> This is problably not a real issue with remoting, but
with the auxiliary
> process. In any case, try starting MD with the
--ipc-tcp option, so it
> will use tcp instead of unix sockets.

I just tried that on a fresh install of SuSE 10.1.
Here is what I got.


% monodevelop --ipc-tcp
which: no mozilla in
(/home/USER/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bi
n:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/usr/lib/jvm/jre/b
in:/usr/lib/mit/bin:
/usr/lib/mit/sbin)

** (mdhost.exe:4625): WARNING **: The class
CompilerGenerated.___callable0 could  not be loaded, used in
Boo.Lang.Interpreter, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=32c39770e9a21a67

============================================================
=====
Got a SIGSEGV while executing native code. This usually
indicates
a fatal error in the mono runtime or one of the native
libraries
used by your application.
============================================================
=====

Stacktrace:

in (wrapper remoting-invoke-with-check)
BooBinding.BooShell.BooShell:___initiali zer () <0x39>
in (wrapper remoting-invoke-with-check)
BooBinding.BooShell.BooShell:___initiali zer ()
<0xffffffc6>
in BooBinding.BooShell.BooShell:.ctor () <0x16>
in (wrapper runtime-invoke)
System.Object:runtime_invoke_void
(object,intptr,int ptr,intptr) <0x511f38ac>
in (wrapper managed-to-native)
System.Reflection.MonoCMethod:InternalInvoke (obj
ect,object[]) <0x4>
in (wrapper managed-to-native)
System.Reflection.MonoCMethod:InternalInvoke (obj
ect,object[])
<0xfffffc25>
in System.Reflection.MonoCMethod:Invoke
(object,System.Reflection.BindingFlags,S
ystem.Reflection.Binder,object[],System.Globalization.Cultur
eInfo)
<0x8d>
in System.Reflection.MonoCMethod:Invoke
(System.Reflection.BindingFlags,System.R
eflection.Binder,object[],System.Globalization.CultureInfo)
<0x1c>
in System.Reflection.ConstructorInfo:Invoke (object[])
<0x35>
in System.Activator:CreateInstance (System.Type,bool)
<0x105>
in System.Activator:CreateInstance (System.Type) <0xc>
in ProcessHost:CreateInstance (System.Type) <0x1f>
in (wrapper remoting-invoke-with-check)
ProcessHost:CreateInstance
(System.Type)  <0xffffff1b>
in ProcessHost:CreateInstance (string,string) <0x33>
in (wrapper runtime-invoke)
System.Object:runtime_invoke_RemoteProcessObject_str
ing_string
(object,intptr,intptr,intptr) <0x511f4906>
in (wrapper managed-to-native)
System.Runtime.Remoting.RemotingServices:Internal Execute
(System.Reflection.MethodBase,object,object[],object[]&)
<0x4>
in (wrapper managed-to-native)
System.Runtime.Remoting.RemotingServices:Internal Execute
(System.Reflection.MethodBase,object,object[],object[]&)
<0xfffffcc0>
in
System.Runtime.Remoting.RemotingServices:InternalExecuteMess
age
(System.Marsh
alByRefObject,System.Runtime.Remoting.Messaging.IMethodCallM
essage)
<0x188>
in
System.Runtime.Remoting.Messaging.StackBuilderSink:SyncProce
ssMessage
(System .Runtime.Remoting.Messaging.IMessage) <0xaf>
in
System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink
:SyncProcessMessa
ge (System.Runtime.Remoting.Messaging.IMessage) <0x5e>
in
System.Runtime.Remoting.Lifetime.LeaseSink:SyncProcessMessag
e
(System.Runtime .Remoting.Messaging.IMessage) <0x25>
in
System.Runtime.Remoting.ClientActivatedIdentity:SyncObjectPr
ocessMessage
(Sys tem.Runtime.Remoting.Messaging.IMessage) <0x9c>
in
System.Runtime.Remoting.Messaging.ServerContextTerminatorSin
k:SyncProcessMess
age (System.Runtime.Remoting.Messaging.IMessage)
<0x139>
in
System.Runtime.Remoting.Contexts.CrossContextChannel:SyncPro
cessMessage
(Syst em.Runtime.Remoting.Messaging.IMessage) <0xd0>
in
System.Runtime.Remoting.Channels.ChannelServices:SyncDispatc
hMessage
(System. Runtime.Remoting.Messaging.IMessage) <0x32>
in System.Runtime.Remoting.Channels.ChannelServicesispatchM
essage
(System.Runt
ime.Remoting.Channels.IServerChannelSinkStack,System.Runtime
.Remoting.Messaging.
IMessage,System.Runtime.Remoting.Messaging.IMessage&)
<0x1e>
in
System.Runtime.Remoting.Channels.ServerDispatchSink:ProcessM
essage
(System.Ru
ntime.Remoting.Channels.IServerChannelSinkStack,System.Runti
me.Remoting.Messagin
g.IMessage,System.Runtime.Remoting.Channels.ITransportHeader
s,System.IO.Stream,S
ystem.Runtime.Remoting.Messaging.IMessage&,System.Runtim
e.Remoting.Channels.ITra
nsportHeaders&,System.IO.Stream&) <0x22>
in
System.Runtime.Remoting.Channels.BinaryServerFormatterSink:P
rocessMessage
(Sy
stem.Runtime.Remoting.Channels.IServerChannelSinkStack,Syste
m.Runtime.Remoting.M
essaging.IMessage,System.Runtime.Remoting.Channels.ITranspor
tHeaders,System.IO.S
tream,System.Runtime.Remoting.Messaging.IMessage&,System
.Runtime.Remoting.Channe
ls.ITransportHeaders&,System.IO.Stream&)
<0x33a>
in
System.Runtime.Remoting.Channels.Tcp.TcpServerTransportSink:
InternalProcessMe
ssage
(System.Runtime.Remoting.Channels.Tcp.ClientConnection)
<0x19f>
in
System.Runtime.Remoting.Channels.Tcp.ClientConnection:Proces
sMessages
() <0xc b>
in (wrapper delegate-invoke)
System.MulticastDelegate:invoke_void ()
<0xffd969e8 >
in
System.Runtime.Remoting.Channels.RemotingThreadPool:PoolThre
ad () <0x168>
in (wrapper delegate-invoke)
System.MulticastDelegate:invoke_void ()
<0xffffff90 >
in (wrapper runtime-invoke)
System.Object:runtime_invoke_void
(object,intptr,int ptr,intptr) <0x50f8b6f5>

Native stacktrace:

        mono(mono_handle_native_sigsegv+0xbb) [0x8150bab]
        mono [0x811fe80]
        [0xffffe440]
        mono(mono_compile_create_var+0x86) [0x8123956]
        mono [0x813b220]
        mono [0x813cad3]
        mono(mono_magic_trampoline+0x1a) [0x8152daa]
        [0xb7bed032]
        [0xb6ee4027]
        [0xb6ee3fa1]
        mono(mono_runtime_invoke_array+0x155) [0x80d7825]
        mono [0x80dc9c5]
        [0xb72707ac]
        [0xb72703a6]
        [0xb727030d]
        [0xb72702c6]
        [0xb715c24e]
        [0xb6edcc7d]
        [0xb6ee3198]
        [0xb6ee3146]
        [0xb6ee301c]
        [0xb6ee2f7c]
        mono(mono_runtime_invoke_array+0x17f) [0x80d784f]
        mono [0x80e1d43]
        [0xb6ee2f1f]
        [0xb6ee2bb1]
        [0xb6ee2648]
        [0xb6ee2507]
        [0xb6ee2366]
        [0xb6ee1fd5]
        [0xb6ee1ed2]
        [0xb6ee1719]
        [0xb6ee129b]
        [0xb6ee114f]
        [0xb6ee1113]
        [0xb6edf253]
        [0xb6ede340]
        [0xb6ede004]
        [0xb7147508]
        [0xb6eddec1]
        [0xb7147508]
        [0xb7147469]
        mono(mono_runtime_delegate_invoke+0x36) [0x80d2b36]
        mono [0x80b41a9]
        mono [0x80fd38e]
        mono [0x8115e35]
        /lib/libpthread.so.0 [0xb7e5c34b]
        /lib/libc.so.6(__clone+0x5e) [0xb7dc665e]

in any case, installing the latest mono has solved this
issue for me.
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
Using version 0.11 on SuSE 10.1
user name
 2006-05-29 12:28:55 
>This is problably not a real issue with remoting, 
>but with the auxiliary process. In any case, try 
>starting MD with the --ipc-tcp option, so it
>will use tcp instead of unix sockets. 

Success! Thanks Lluis and marumoto, installing the latest
mono runtime and
using the option above solved the problem.

-- 
Patrick Philippot
MainSoft Consulting Services
www.mainsoft.fr

-----Original Message-----
From: Lluis Sanchez [mailto:lluisximian.com] 
Sent: Monday, May 29, 2006 11:34 AM
To: Contact
Cc: monodevelop-listlists.ximian.com
Subject: Re: [MonoDevelop] Using version 0.11 on SuSE 10.1

This is problably not a real issue with remoting, but with
the auxiliary
process. In any case, try starting MD with the --ipc-tcp
option, so it
will use tcp instead of unix sockets.

El dg 28 de 05 del 2006 a les 18:19 +0200, en/na Contact va
escriure:
> Hi,
>  
> I have installed MD 0.11 on a fresh install of SuSE
10.1 and I get the
> follwoing error message upon startup:
>  
> System.Runtime.Remoting.RemotingException: Unix
transport error.
> 
> Server stack trace: 
> in <0x0008f>
Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveMessageStat
us
> (System.IO.Stream networkStream, System.Byte[] buffer)
> in <0x0017c>
>
Mono.Remoting.Channels.Unix.UnixClientTransportSink:ProcessM
essage
(IMessage
> msg, ITransportHeaders requestHeaders, System.IO.Stream
requestStream,
> ITransportHeaders responseHeaders, System.IO.Stream
responseStream)
> in <0x0024c>
>
Mono.Remoting.Channels.Unix.UnixBinaryClientFormatterSink:Sy
ncProcessMessage
> (IMessage msg)
> 
> Exception rethrown at [0]: 
> ---> System.Runtime.Remoting.RemotingException:
Connection closed
> in <0x0006c>
Mono.Remoting.Channels.Unix.UnixMessageIO:StreamRead
> (System.IO.Stream networkStream, System.Byte[] buffer,
Int32 count)
> in <0x00044>
Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveMessageStat
us
> (System.IO.Stream networkStream, System.Byte[]
buffer)--- End of inner
> exception stack trace ---
> 
> in <0x0008f>
Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveMessageStat
us
> (System.IO.Stream networkStream, System.Byte[] buffer)
> in <0x0017c>
>
Mono.Remoting.Channels.Unix.UnixClientTransportSink:ProcessM
essage
(IMessage
> msg, ITransportHeaders requestHeaders, System.IO.Stream
requestStream,
> ITransportHeaders responseHeaders, System.IO.Stream
responseStream)
> in <0x0024c>
>
Mono.Remoting.Channels.Unix.UnixBinaryClientFormatterSink:Sy
ncProcessMessage
> (IMessage msg)
> 
> Any idea? I'm wondering why MD needs to call into the
Remoting classes
upon
> startup.
> 
> Thanks in advance.
> 


_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )