We have a few photon applications running in the foreground and our servo
running in the background. When, we increase the priority of our servo,
photon really slows down. I would like to increase the priority of photon. I
tried increasing the priority of the photon window manager"pwm" but it made
no difference. Which process controls the photon apps?
I would apprecaite your input.
Thanks,
Shashank
Sounds like you have a more fundamental problem. When just
the servo program is running, what’s the CPU load?
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
Yes, I do use the usemsg, and also ldrel to place my own QNX_info
section. As soon as I disable them the .note section is filled with
01.01. I can even delete the this section after I call usemsg and
ldrel. Actually, it is fine with me if any information is plased
there. What wonders me is why that data is taken as a process name.
Ultimately this is not the expected behavior. I have filed a PR for this.
I’ve noticed that the problem happens when using ldrel. usemsg, by
default, uses ldrel to insert the use message into the binary. By
supplying the -o argument to usemsg you can force it to use objcopy.
This is the make project (with qconfig.mk, qtargets.mk, and etc.) on
self-hosted Neutrino (6.3.0 SP2) platform.
If usemsg -o is an acceptable workaround for you you can insert the
following into your common.mk to have the build system invoke usemsg
with the -o parameter:
dxwangwrote:
I want to print the percent of cpu for idle process in my c program.
if pclose(ptr) is used (this means I just want hogs run only
once). the program can’t print the message I want, just print the
message about the broken pipe. (if use fd , the program run
correctly. I know this problem occurs because hogs update message
every 3 seconds . but I just want to print message only once.)
if pclose(ptr) isn’t used (this means print the message all the
time ) , the program can’t print the message immediately. I have
tried fflush(stdout) and setvbuf为_IONBF，but still can’t solve it
I don’t know how to slove this two programs. Thanks.