> I've narrowed it down to a call in threads.c, line 766: > > pthread_getattr_np(pthread_self(), &attr). > > I'm still no wiser though. Does anyone have any insight as to why this > call might be causing some kind of deadlock?
Look very carefully at what happens with that attribute resource structure. Is it getting re-used for the second call that causes the deadlock? How is it allocated? -- John Dallman Parasolid Porting Engineer Siemens PLM Software 46 Regent Street, Cambridge, CB2 1DP United Kingdom Tel: +44-1223-371554 [EMAIL PROTECTED] www.siemens.com/plm > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:mono-list- > [EMAIL PROTECTED] On Behalf Of simozzer > Sent: Sunday, August 17, 2008 11:14 PM > To: [email protected] > Subject: Re: [Mono-list] Can run mono once and only once ( Mono locks > up when calling pthread_getattr_np ). > > > I've narrowed it down to a call in threads.c, line 766: > > pthread_getattr_np(pthread_self(), &attr). > > I'm still no wiser though. Does anyone have any insight as to why this > call > might be causing some kind of deadlock? > > Thanks > > Simozzer. > > > > simozzer wrote: > > > > Can anyone please help me here? > > > > I can run mono 1.2.6 absolutely fine with no problems but with 2.0 I > > always experience a lock-up. The lockup occurs both when I have built > mono > > from trunk and also when i try installing the (unsupported) binary > > distribution. > > > > Any hints to help me debug this would be much appreciated. > > > > Cheers > > > > Mozzy > > > > > > simozzer wrote: > >> > >> Hello, > >> > >> I wonder if anyone can help me with fixing this? > >> > >> After lots of package upgrades I've finally managed to get mono 2.0 > >> installed on my EEE PC -Yey! > >> > >> It seems, however, I can run any mono application once then I have > to > >> reboot - Boo! > >> > >> After reboot the first mono application i try to run runs fine - the > next > >> freezes :( > >> > >> I've tried debugging using gdb but i've never gdb debugged anything > in my > >> life so I haven't got very far. Here follows the gdb output from two > >> successive runs of HelloWorld.exe: > >> > >> Starting program: /opt/mono/2.0/bin/mono /home/user/HelloWorld.exe > >> [Thread debugging using libthread_db enabled] > >> [New Thread -1210984736 (LWP 8969)] > >> [New Thread -1218667600 (LWP 8970)] > >> [New Thread -1218815056 (LWP 8971)] > >> Hello > >> > >> Program received signal SIGPWR, Power fail/restart. > >> [Switching to Thread -1218815056 (LWP 8971)] > >> 0xb7e7dc01 in pthread_cond_wait@@GLIBC_2.3.2 () from > >> /lib/tls/libpthread.so.0 > >> (gdb) continue > >> Continuing. > >> > >> Program received signal SIGXCPU, CPU time limit exceeded. > >> 0xb7d47e3d in sigsuspend () from /lib/tls/libc.so.6 > >> (gdb) c > >> Continuing. > >> > >> Program exited normally. > >> (gdb) run /home/user/HelloWorld.exe > >> Starting program: /opt/mono/2.0/bin/mono /home/user/HelloWorld.exe > >> [Thread debugging using libthread_db enabled] > >> [New Thread -1210964256 (LWP 8972)] > >> [New Thread -1218647120 (LWP 8973)] > >> > >> At this point gdb freezes - what keys can i press to halt execution > and > >> inspect the call stack to find out what the heck is happening? > >> > >> Can anyone help? P.lease, it would be wonderful to get Mono and > >> MonoDevelop up and running on a 4GB handheld 'toy' :o) > >> > >> Cheers > >> > >> Mozzy > >> > >> > >> > >> > >> > >> > >> > >> > > > > > > -- > View this message in context: http://www.nabble.com/Can-run-mono-once- > and-only-once-%28EEE-PC%29--tp18821807p19023849.html > Sent from the Mono - General mailing list archive at Nabble.com. > > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
