It goes like this.
We have an application that we have built with QNX4.24. We have used
this application for several years running with photon1.12 and
X-windows. Do to the updating of QNX we have decided to move to the
newer QNX4.25 and photon1.14. I have made minor modification to the
directory structure and change some define names. I have tested the
newly created code on the QNX4.24/photon1.12 and it work just fine. On
the QNX4.25/photon1.14 system the code fails. During debug I was able
to determine the location of the failure is at the QNX command
‘execl(PATH, application, arg1, arg2, NULL)’. I have been able to debug
up to this point. Once this point is reached the an attempt to start the
new application is made and the debug session is finished. The display
screen goes blank and nothing else happens. I have to do an
‘ALT-DEL-SHIFT-BACKSPACE’ TO GET BACK TO A WORKING SYSTEM. In the
4.24/1.12 system the application continue correctly, in the 4.25/1.14
system the application appears to lock up. I have compared the data
being loaded prior to the ‘execl’ command on both systems. The data is
the same in both.
I guess at this point with our testing I’m not sure where to go. I guess
the first question would be, have QNX made modification to the ‘execl’
function? Or have QNX made modifications to the OS that would cause this
type of problem? Could I have a setup problem with some part of QNX4.25
that needs to be made? Is there any further testing I could do to prove
out where the error may lye? Is there more information I can give you?
If you could help me out here that would be great.
Hope to hear from someone soon.
By “the display screen goes blank” i am assuming that there is no Photon GUI
image present. When you go back to the working system check to see if the
“pwm” and/or the “PG.xxx” video drivers are still running. By being able to
type in the ALT-DEL-SHIFT-BACKSPACE i think “pwm” is still running
so it may be that the video driver has terminated. It may be that somthing
in the
new child app is blowing things out of the water. By the way is the child
app
running when you return to the console? Hope this might help you get some
clue as to your problem.
Ivan
John Parsons <parsonsj@esi.com> wrote in message
news:39AE60F1.B3DD8516@esi.com…
It goes like this.
We have an application that we have built with QNX4.24. We have used
this application for several years running with photon1.12 and
X-windows. Do to the updating of QNX we have decided to move to the
newer QNX4.25 and photon1.14. I have made minor modification to the
directory structure and change some define names. I have tested the
newly created code on the QNX4.24/photon1.12 and it work just fine. On
the QNX4.25/photon1.14 system the code fails. During debug I was able
to determine the location of the failure is at the QNX command
‘execl(PATH, application, arg1, arg2, NULL)’. I have been able to debug
up to this point. Once this point is reached the an attempt to start the
new application is made and the debug session is finished. The display
screen goes blank and nothing else happens. I have to do an
‘ALT-DEL-SHIFT-BACKSPACE’ TO GET BACK TO A WORKING SYSTEM. In the
4.24/1.12 system the application continue correctly, in the 4.25/1.14
system the application appears to lock up. I have compared the data
being loaded prior to the ‘execl’ command on both systems. The data is
the same in both.
I guess at this point with our testing I’m not sure where to go. I guess
the first question would be, have QNX made modification to the ‘execl’
function? Or have QNX made modifications to the OS that would cause this
type of problem? Could I have a setup problem with some part of QNX4.25
that needs to be made? Is there any further testing I could do to prove
out where the error may lye? Is there more information I can give you?
If you could help me out here that would be great.
Hope to hear from someone soon.
\
Okay
When the screen goes blank there is not Photon GUI. After I do the
ALT-DEL-SHIFT-BACKSPACE and return to standard system operation. Every thing
has been slain (no pwm, pdm, Pg.chips or child app). There is a wd running
waiting for
a recv, and one dead zombie process . The child process is not running. The
reset are as they where prior to going into photon. Do remember this same code
works with QNX4.24. The data being set for the child process appears to be the
same for both OS versions.
John
Ivan Bannon wrote:
By “the display screen goes blank” i am assuming that there is no Photon GUI
image present. When you go back to the working system check to see if the
“pwm” and/or the “PG.xxx” video drivers are still running. By being able to
type in the ALT-DEL-SHIFT-BACKSPACE i think “pwm” is still running
so it may be that the video driver has terminated. It may be that somthing
in the
new child app is blowing things out of the water. By the way is the child
app
running when you return to the console? Hope this might help you get some
clue as to your problem.
Ivan
John Parsons <> parsonsj@esi.com> > wrote in message
news:> 39AE60F1.B3DD8516@esi.com> …
It goes like this.
We have an application that we have built with QNX4.24. We have used
this application for several years running with photon1.12 and
X-windows. Do to the updating of QNX we have decided to move to the
newer QNX4.25 and photon1.14. I have made minor modification to the
directory structure and change some define names. I have tested the
newly created code on the QNX4.24/photon1.12 and it work just fine. On
the QNX4.25/photon1.14 system the code fails. During debug I was able
to determine the location of the failure is at the QNX command
‘execl(PATH, application, arg1, arg2, NULL)’. I have been able to debug
up to this point. Once this point is reached the an attempt to start the
new application is made and the debug session is finished. The display
screen goes blank and nothing else happens. I have to do an
‘ALT-DEL-SHIFT-BACKSPACE’ TO GET BACK TO A WORKING SYSTEM. In the
4.24/1.12 system the application continue correctly, in the 4.25/1.14
system the application appears to lock up. I have compared the data
being loaded prior to the ‘execl’ command on both systems. The data is
the same in both.
I guess at this point with our testing I’m not sure where to go. I guess
the first question would be, have QNX made modification to the ‘execl’
function? Or have QNX made modifications to the OS that would cause this
type of problem? Could I have a setup problem with some part of QNX4.25
that needs to be made? Is there any further testing I could do to prove
out where the error may lye? Is there more information I can give you?
If you could help me out here that would be great.
Hope to hear from someone soon.
\
John Parsons <parsonsj@esi.com> wrote in message
news:39AE60F1.B3DD8516@esi.com…
It goes like this.
We have an application that we have built with QNX4.24. We have used
this application for several years running with photon1.12 and
X-windows. Do to the updating of QNX we have decided to move to the
newer QNX4.25 and photon1.14. I have made minor modification to the
directory structure and change some define names. I have tested the
newly created code on the QNX4.24/photon1.12 and it work just fine. On
the QNX4.25/photon1.14 system the code fails. During debug I was able
I think, you need to use PtSpawn () function or its relatives.
Using functions spawn…() (and exec…()) is disabled now in any Photon
1.14
program. I also have a program which runs in Photon 1.12 smoothly,
but in Photon 1.14 it terminated, so I had to rewrite it. I do not know,
why these functions were disabled in Photon programs (in QNX programs
functions spawn () and exec () are working OK). Hope, reasons for disabling
were worth-while, because necessity to rewrite a correct program is very
irritating (and very time-consuming).
V. Ivashko ivvon@alice.dp.ua