TeamForge : Post

Forum Topic - Thead naming:

View: as

Zhenwang Yao

01/23/2008 6:09 PM

post4546

qnx 6.3.2 kernel now supports naming of a thread via function
pthread_setname_np()

I have problem using this function when debugging in Momentics IDE, and it gives me error code EBUSY ("Device or 
resource busy").

But when I run (instead of debugging) in IDE, it works fine. And, if I run the binary directly on a QNX target, it also 
works just fine. 

Any idea?

My Momentics is carried on a WindowXp machine.

Thanks.

Elena Laskavaia

01/24/2008 10:10 AM

post4556

RE: Thead naming

What is the target platform? X86? Does you host installation matches with
target (version)? Could be some weird binary incompatibility with
debugger...

(I used this function without any problems in my setup)

Brian K Hlady(deleted)

01/24/2008 10:17 AM

post4557

RE: Thead naming

Hi Zhenwang,

What you're seeing is a known issue, and is covered under PR/38578:

pthread_setname_np fails with child resource busy when debugging in IDE

This is a kernel issue, and scheduled to be fixed in a future release. If
you require a fix in the short term, please contact your QSS sales
representative and discuss support options.

Cheers,
-Brian 

> -----Original Message-----
> From: Elena Laskavaia [mailto:elaskavaia@qnx.com] 
> Sent: Thursday, January 24, 2008 10 11
> To: momentics-community
> Subject: RE: Thead naming
> 
> What is the target platform? X86? Does you host installation 
> matches with
> target (version)? Could be some weird binary incompatibility with
> debugger...
> 
> (I used this function without any problems in my setup)
> 
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post4556
>

Zhenwang Yao

01/24/2008 11:15 AM

post4561

Re: RE: Thead naming

Hi Brian,

Thank you very much!

Zhenwang.

> Hi Zhenwang,
> 
> What you're seeing is a known issue, and is covered under PR/38578:
> 
> pthread_setname_np fails with child resource busy when debugging in IDE
> 
> This is a kernel issue, and scheduled to be fixed in a future release. If
> you require a fix in the short term, please contact your QSS sales
> representative and discuss support options.
> 
> Cheers,
> -Brian 
>

Return