sin

How come sin can be SEND block on a process, forever ?

  • Mario

It’s on my list…I’ve noticed that Xphoton apps tend to do it on a
fairly repeatable basis. It’s strange though because there doesn’t really
seem to be any reason for it. I’ll see what I can do when I have some more
time.

cheers,

Kris

Mario Charest <mcharest@zinformatic.com> wrote:


How come sin can be SEND block on a process, forever ?

  • Mario


Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“You’re bound to be unhappy if you optimize everything” - Donald Knuth

“Kris Eric Warkentin” <kewarken@qnx.com> wrote in message
news:9j9vjd$33c$1@nntp.qnx.com

It’s on my list…I’ve noticed that Xphoton apps tend to do it on a
fairly repeatable basis. It’s strange though because there doesn’t really
seem to be any reason for it. I’ll see what I can do when I have some
more
time.

It does it for me (with 6.1 only) on a USB driver I wrote based on the
printer DDK.
One of the think I still have to chase about this program is that pidin show
a different
name then the executable name.

cheers,

Kris

Mario Charest <> mcharest@zinformatic.com> > wrote:


How come sin can be SEND block on a process, forever ?

  • Mario





    Kris Warkentin
    kewarken@qnx.com
    (613)591-0836 x9368
    “You’re bound to be unhappy if you optimize everything” - Donald Knuth

Hi mario,

For me, sin keeps coredumping on my SMP system…

Regards…


“Mario Charest” <mcharest@zinformatic.com> wrote in message
news:9j9l80$bc2$1@inn.qnx.com

How come sin can be SEND block on a process, forever ?

  • Mario

Just so that all the QNX4 veterans know, however, sin is really NOT the
program to use anymore. It exists but the proper QNX6 utility to use is
pidin. I’m not saying sin is unsupported, it’s just that bugs in it
tend to get a little lower priority than some other things.

cheers,

Kris

jhr <nospam@nospam.com> wrote:

Hi mario,

For me, sin keeps coredumping on my SMP system…

Regards…



“Mario Charest” <> mcharest@zinformatic.com> > wrote in message
news:9j9l80$bc2$> 1@inn.qnx.com> …


How come sin can be SEND block on a process, forever ?

  • Mario
    \


Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“You’re bound to be unhappy if you optimize everything” - Donald Knuth

Mario Charest <mcharest@zinformatic.com> wrote:


How come sin can be SEND block on a process, forever ?

  • Mario

I fixed a bug recently which caused sin to hang on programs which had done
something to their arguments. If you had a program such as tin running and
did a ‘sin’, sin would sit and spin (not SEND blocked however…). The bug
actually manifests itself in ‘pidin arg’ as well - they each have a section
of code which is similar. Either way, they weren’t taking into account that
a read() could return 0 in some cases and not breaking out of the loop.

It may be that your problem had something to do with this and will go away
but without some form of repeatable case, it’s hard for me to find the
problem.

cheers,

Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“Computer science is no more about computers than astronomy is about telescopes”
–E.W.Dijkstra