During startup of a program I’m working, itl terminate at random point
during some of the many share object constructor. When it terminates, the
message “Killed” is displayed. I didn’t find that string in all of the
project file (c, .h, etc). I was wondering if anybody might have an idea
where that message could be coming from?
“Mario Charest” postmaster@127.0.0.1 wrote in message
news:cqdi4r$s7r$1@inn.qnx.com…
During startup of a program I’m working, itl terminate at random point
during some of the many share object constructor. When it terminates, the
message “Killed” is displayed. I didn’t find that string in all of the
project file (c, .h, etc). I was wondering if anybody might have an idea
where that message could be coming from?
Found it, it’s upon reception of kill signal 
- Mario
Mario Charest postmaster@127.0.0.1 wrote:
“Mario Charest” postmaster@127.0.0.1 wrote in message
news:cqdi4r$s7r$> 1@inn.qnx.com> …
During startup of a program I’m working, itl terminate at random point
during some of the many share object constructor. When it terminates, the
message “Killed” is displayed. I didn’t find that string in all of the
project file (c, .h, etc). I was wondering if anybody might have an idea
where that message could be coming from?Found it, it’s upon reception of kill signal >
Yup, and probably printed by the shell, not your program.
David Gibbs
QNX Training Services
dagibbs@qnx.com
“David Gibbs” <dagibbs@qnx.com> wrote in message
news:cqeku4$lkd$1@inn.qnx.com…
Mario Charest postmaster@127.0.0.1 wrote:
“Mario Charest” postmaster@127.0.0.1 wrote in message
news:cqdi4r$s7r$> 1@inn.qnx.com> …
During startup of a program I’m working, itl terminate at random point
during some of the many share object constructor. When it terminates,
the
message “Killed” is displayed. I didn’t find that string in all of the
project file (c, .h, etc). I was wondering if anybody might have an
idea
where that message could be coming from?Found it, it’s upon reception of kill signal >
Yup, and probably printed by the shell, not your program.
Yes. That’s the kind of thing that’s hard to document. Maybe the message
could be improved, like “killed signal”.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
Do you run procnto with at least one ‘-v’? Then proc should dump out some helpful info (like Process foobar terminated with signal SIGKILL etc.)
-Jay.
Mario Charest wrote:
“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cqeku4$lkd$> 1@inn.qnx.com> …Mario Charest postmaster@127.0.0.1 wrote:
“Mario Charest” postmaster@127.0.0.1 wrote in message
news:cqdi4r$s7r$> 1@inn.qnx.com> …
During startup of a program I’m working, itl terminate at random point
during some of the many share object constructor. When it terminates,
the
message “Killed” is displayed. I didn’t find that string in all of the
project file (c, .h, etc). I was wondering if anybody might have an
idea
where that message could be coming from?Found it, it’s upon reception of kill signal >
Yup, and probably printed by the shell, not your program.
Yes. That’s the kind of thing that’s hard to document. Maybe the message
could be improved, like “killed signal”.-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
“Jay Greig” <greig@qnx.com> wrote in message
news:cqf3dd$1fg$1@inn.qnx.com…
Do you run procnto with at least one ‘-v’? Then proc should dump out some
helpful info (like Process foobar terminated with signal SIGKILL etc.)
Yes. All I get is “Killed”
-Jay.
Mario Charest wrote:
“David Gibbs” <> dagibbs@qnx.com> > wrote in message
news:cqeku4$lkd$> 1@inn.qnx.com> …Mario Charest postmaster@127.0.0.1 wrote:
“Mario Charest” postmaster@127.0.0.1 wrote in message
news:cqdi4r$s7r$> 1@inn.qnx.com> …
During startup of a program I’m working, itl terminate at random point
during some of the many share object constructor. When it terminates,
the
message “Killed” is displayed. I didn’t find that string in all of the
project file (c, .h, etc). I was wondering if anybody might have an
idea
where that message could be coming from?Found it, it’s upon reception of kill signal >
Yup, and probably printed by the shell, not your program.
Yes. That’s the kind of thing that’s hard to document. Maybe the
message could be improved, like “killed signal”.-David
David Gibbs
QNX Training Services
dagibbs@qnx.com
Jay Greig <greig@qnx.com> wrote:
JG > Do you run procnto with at least one ‘-v’? Then proc should dump out some helpful info (like Process foobar terminated with signal SIGKILL etc.)
JG > -Jay.
Good. Is that documented anywhere?
Bill Caroselli <qtps@earthlink.net> wrote:
Jay Greig <> greig@qnx.com> > wrote:
JG > Do you run procnto with at least one ‘-v’? Then proc should dump out some helpful info (like Process foobar terminated with signal SIGKILL etc.)JG > -Jay.
Good. Is that documented anywhere?
It is now. 