[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
THREADSAFE
From: "Malin Andersson" ####@####.#### Date: 1 Mar 2006 13:35:16 +0000 Message-Id: <16679.81.186.245.19.1141220113.squirrel@c-91e970d5.015-15-6c756e10.cust.bredbandsbolaget.se> Hi Greg, I have a little problem. I am trying to make a small nano-X application. I have two threads - one sleeping inside GrGetNextEvent and one who is trying to make the other wake up by calling GrInjectKeyboardEvent. I have enabled THREADSAFE mode but this results in that GrInjectKeyboardEvent is blocked by LOCK(&nxGlobalLock), which is locked by the sleeping GrGetNextEvent. Is it safe to run this without THREADSAFE mode? If not, is there another way to make the GrGetNextEvent thread wake up? Thank you very much in advance! Best regards, Malin -- ------------------------------------------------------ Malin Andersson ####@####.#### Dag Hammarskjölds väg 5D, 224 64 Lund telnr: +46 46 211 81 03, mobilnr: +46 70 330 72 59 -- ------------------------------------------------------ Malin Andersson ####@####.#### ICQ: 45 79 33 79 Dag Hammarskjölds väg 5D, 224 64 Lund telnr: +46 46 211 81 03, mobilnr: +46 70 330 72 59 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
THREADSAFE
From: "Malin Andersson" ####@####.#### Date: 1 Mar 2006 13:32:12 +0000 Message-Id: <16665.81.186.245.19.1141219930.squirrel@c-91e970d5.015-15-6c756e10.cust.bredbandsbolaget.se> Hi Greg, I have a little problem. I am trying to make a small nano-X application. I have two threads - one sleeping inside GrGetNextEvent and one who is trying to make the other wake up by calling GrInjectKeyboardEvent. I have enabled THREADSAFE mode but this results in that GrInjectKeyboardEvent is blocked by LOCK(&nxGlobalLock), which is locked by the sleeping GrGetNextEvent. Is it safe to run this without THREADSAFE mode? If not, is there another way to make the GrGetNextEvent thread wake up? Thank you very much in advance! Best regards, Malin -- ------------------------------------------------------ Malin Andersson ####@####.#### Dag Hammarskjölds väg 5D, 224 64 Lund telnr: +46 46 211 81 03, mobilnr: +46 70 330 72 59 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] THREADSAFE
From: "Greg Haerr" ####@####.#### Date: 1 Mar 2006 22:13:52 +0000 Message-Id: <27ce01c63d7d$631cb570$6401a8c0@winXP> : I have a little problem. I am trying to make a small nano-X application. I : have two threads - one sleeping inside GrGetNextEvent and one who is : trying to make the other wake up by calling GrInjectKeyboardEvent. I have : enabled THREADSAFE mode but this results in that GrInjectKeyboardEvent is : blocked by LOCK(&nxGlobalLock), which is locked by the sleeping : GrGetNextEvent. Is it safe to run this without THREADSAFE mode? If not, is : there another way to make the GrGetNextEvent thread wake up? It looks like you're going to have to run this without THREADSAFE. Both calls eventually call nxFlushReq, which LOCKs the global lock again, so commenting out the LOCK in GrInjectKeyboardEvent won't work. I think you should be OK, since GrInjectKeyboardEvent only sends data to the server, and never waits for a reply; this is where the two could otherwise get unsynchronized. Regards, Greg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: [nanogui] THREADSAFE
From: "Robbie" ####@####.#### Date: 23 Mar 2006 20:35:05 +0000 Message-Id: <20060323203457.7F9208A19C@xprdmxin.myway.com> Sorry Guys. I hate when a message has no subject to I'm resending this. --Robbie --- On Thu 03/23, Robbie < ####@####.#### > wrote: From: Robbie [mailto: ####@####.#### To: ####@####.#### ####@####.#### ####@####.#### Date: Thu, 23 Mar 2006 15:09:55 -0500 Subject: I'm not sure if this question will apply to the below comments because it's slightly different. The problem I'm having is that the thread runs as expected but it's looks like my main loop is halted. It will eventually continue after a few minutes then would halt again. This repeats several times. Thread safe mode is enabled. Any thoughts why this occurs? Thanks, Robbie > -----Original Message----- > From: Greg Haerr ####@####.#### > Sent: Wednesday, March 01, 2006 4:13 PM > To: Malin Andersson; ####@####.#### > Subject: Re: [nanogui] THREADSAFE > > : I have a little problem. I am trying to make a small nano-X application. > I > : have two threads - one sleeping inside GrGetNextEvent and one who is > : trying to make the other wake up by calling GrInjectKeyboardEvent. I > have > : enabled THREADSAFE mode but this results in that GrInjectKeyboardEvent > is > : blocked by LOCK(&nxGlobalLock), which is locked by the sleeping > : GrGetNextEvent. Is it safe to run this without THREADSAFE mode? If not, > is > : there another way to make the GrGetNextEvent thread wake up? > > It looks like you're going to have to run this without > THREADSAFE. Both calls eventually call nxFlushReq, > which LOCKs the global lock again, so commenting out > the LOCK in GrInjectKeyboardEvent won't work. > > I think you should be OK, since GrInjectKeyboardEvent only > sends data to the server, and never waits for a reply; this is > where the two could otherwise get unsynchronized. > > Regards, > > Greg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ####@####.#### > For additional commands, e-mail: ####@####.#### _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: [nanogui] THREADSAFE
From: "Robbie" ####@####.#### Date: 27 Mar 2006 16:09:13 +0100 Message-Id: <20060327150906.693A7299B6@xprdmailfe21.nwk.excite.com> Hi All, I haven't resolve this problem. I can't seem to find a good doc on pthread that would help me figure out if this is a user configuration error or it's a nanogui problem. Any ideas? > -----Original Message----- > From: Robbie ####@####.#### > Sent: Thursday, March 23, 2006 2:35 PM > To: ####@####.#### ####@####.#### ####@####.#### > Subject: RE: [nanogui] THREADSAFE > > > Sorry Guys. > I hate when a message has no subject to I'm resending this. > --Robbie > > --- On Thu 03/23, Robbie < ####@####.#### > wrote: > From: Robbie [mailto: ####@####.#### > To: ####@####.#### ####@####.#### ####@####.#### > Date: Thu, 23 Mar 2006 15:09:55 -0500 > Subject: > > I'm not sure if this question will apply to the below comments because > it's slightly different. > The problem I'm having is that the thread runs as expected but it's looks > like my main loop is halted. It will eventually continue after a few > minutes then would halt again. > This repeats several times. Thread safe mode is enabled. > > Any thoughts why this occurs? > > Thanks, > Robbie > > > -----Original Message----- > > From: Greg Haerr ####@####.#### > > Sent: Wednesday, March 01, 2006 4:13 PM > > To: Malin Andersson; ####@####.#### > > Subject: Re: [nanogui] THREADSAFE > > > > : I have a little problem. I am trying to make a small nano-X > application. > > I > > : have two threads - one sleeping inside GrGetNextEvent and one who is > > : trying to make the other wake up by calling GrInjectKeyboardEvent. I > > have > > : enabled THREADSAFE mode but this results in that GrInjectKeyboardEvent > > is > > : blocked by LOCK(&nxGlobalLock), which is locked by the sleeping > > : GrGetNextEvent. Is it safe to run this without THREADSAFE mode? If > not, > > is > > : there another way to make the GrGetNextEvent thread wake up? > > > > It looks like you're going to have to run this without > > THREADSAFE. Both calls eventually call nxFlushReq, > > which LOCKs the global lock again, so commenting out > > the LOCK in GrInjectKeyboardEvent won't work. > > > > I think you should be OK, since GrInjectKeyboardEvent only > > sends data to the server, and never waits for a reply; this is > > where the two could otherwise get unsynchronized. > > > > Regards, > > > > Greg > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: ####@####.#### > > For additional commands, e-mail: ####@####.#### > > > > > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ####@####.#### > For additional commands, e-mail: ####@####.#### _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
RE: [nanogui] THREADSAFE
From: "Robbie" ####@####.#### Date: 27 Mar 2006 20:41:57 +0100 Message-Id: <20060327194143.B5486299AF@xprdmailfe21.nwk.excite.com> I believe I have solved this problem. However, I'm looking for a way for an event to interrupt the current thread whatever that may be. Does anyone have any ideas how to use event to handle this? Thanks, --Robbie > -----Original Message----- > From: Robbie ####@####.#### > Sent: Monday, March 27, 2006 9:09 AM > To: ####@####.#### > Subject: RE: [nanogui] THREADSAFE > > > Hi All, > I haven't resolve this problem. I can't seem to find a good doc on pthread > that would help me figure out if this is a user configuration error or > it's a nanogui problem. > Any ideas? > > > > -----Original Message----- > > From: Robbie ####@####.#### > > Sent: Thursday, March 23, 2006 2:35 PM > > To: ####@####.#### ####@####.#### ####@####.#### > > Subject: RE: [nanogui] THREADSAFE > > > > > > Sorry Guys. > > I hate when a message has no subject to I'm resending this. > > --Robbie > > > > --- On Thu 03/23, Robbie < ####@####.#### > wrote: > > From: Robbie [mailto: ####@####.#### > > To: ####@####.#### ####@####.#### ####@####.#### > > Date: Thu, 23 Mar 2006 15:09:55 -0500 > > Subject: > > > > I'm not sure if this question will apply to the below comments because > > it's slightly different. > > The problem I'm having is that the thread runs as expected but it's > looks > > like my main loop is halted. It will eventually continue after a few > > minutes then would halt again. > > This repeats several times. Thread safe mode is enabled. > > > > Any thoughts why this occurs? > > > > Thanks, > > Robbie > > > > > -----Original Message----- > > > From: Greg Haerr ####@####.#### > > > Sent: Wednesday, March 01, 2006 4:13 PM > > > To: Malin Andersson; ####@####.#### > > > Subject: Re: [nanogui] THREADSAFE > > > > > > : I have a little problem. I am trying to make a small nano-X > > application. > > > I > > > : have two threads - one sleeping inside GrGetNextEvent and one who is > > > : trying to make the other wake up by calling GrInjectKeyboardEvent. I > > > have > > > : enabled THREADSAFE mode but this results in that > GrInjectKeyboardEvent > > > is > > > : blocked by LOCK(&nxGlobalLock), which is locked by the sleeping > > > : GrGetNextEvent. Is it safe to run this without THREADSAFE mode? If > > not, > > > is > > > : there another way to make the GrGetNextEvent thread wake up? > > > > > > It looks like you're going to have to run this without > > > THREADSAFE. Both calls eventually call nxFlushReq, > > > which LOCKs the global lock again, so commenting out > > > the LOCK in GrInjectKeyboardEvent won't work. > > > > > > I think you should be OK, since GrInjectKeyboardEvent only > > > sends data to the server, and never waits for a reply; this is > > > where the two could otherwise get unsynchronized. > > > > > > Regards, > > > > > > Greg > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: ####@####.#### > > > For additional commands, e-mail: ####@####.#### > > > > > > > > > > _______________________________________________ > > Join Excite! - http://www.excite.com > > The most personalized portal on the Web! > > > > _______________________________________________ > > Join Excite! - http://www.excite.com > > The most personalized portal on the Web! > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: ####@####.#### > > For additional commands, e-mail: ####@####.#### > > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ####@####.#### > For additional commands, e-mail: ####@####.#### _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |