qpWave - Segmentation fault (core dumped) #92
Comments
|
qpAdm calls qpfstats which must be in your path
The key error line in your output is
qpfstats not found
Nick
…Sent from my iPhone
On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
Hello,
When I run qpWave in AdmixTools, I met a error: segmentation fault (core dumped)
Here is the error message
qpWave version: 1520
*** recommended that inbreed be explicitly set ***
inbreed set YES
tmp: /tmp/fsx.7302
sh: 1: qpfstats: not found
bad open /tmp/fsx.7302
(openit) can't open file /tmp/fsx.7302 of type r
error info: No such file or directory
Segmentation fault (core dumped)
What's wrong with it?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
|
Dear Nick
Hello, Thank you for your reply
But, I actually have the qpfstats file, but why the program cannot find
qpfstats?
What should I do? Is there any problem in my files?
- Jonghyun Kim -
[image: image.png]
2022년 6월 21일 (화) 오후 10:36, bumblenick ***@***.***>님이 작성:
… qpAdm calls qpfstats which must be in your path
The key error line in your output is
qpfstats not found
Nick
Sent from my iPhone
> On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
>
>
> Hello,
> When I run qpWave in AdmixTools, I met a error: segmentation fault (core
dumped)
> Here is the error message
>
> qpWave version: 1520
>
> *** recommended that inbreed be explicitly set ***
> inbreed set YES
> tmp: /tmp/fsx.7302
> sh: 1: qpfstats: not found
> bad open /tmp/fsx.7302
> (openit) can't open file /tmp/fsx.7302 of type r
> error info: No such file or directory
> Segmentation fault (core dumped)
>
> What's wrong with it?
>
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you are subscribed to this thread.
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUI4QZQWK7P4OEGANJRMLU3VQHAMVANCNFSM5ZMKI2OQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Before you run qpWave please just run qpfstats (no parameters)
You should see something like:
no parameters
## qpfstats version: 735
but I suspect you will get qpfstats: command not found
On Tue, Jun 21, 2022 at 6:54 PM Jonghyun Kim ***@***.***>
wrote:
… Dear Nick
Hello, Thank you for your reply
But, I actually have the qpfstats file, but why the program cannot find
qpfstats?
What should I do? Is there any problem in my files?
- Jonghyun Kim -
[image: image.png]
2022년 6월 21일 (화) 오후 10:36, bumblenick ***@***.***>님이 작성:
> qpAdm calls qpfstats which must be in your path
> The key error line in your output is
> qpfstats not found
>
> Nick
>
>
> Sent from my iPhone
>
> > On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
> >
> >
> > Hello,
> > When I run qpWave in AdmixTools, I met a error: segmentation fault
(core
> dumped)
> > Here is the error message
> >
> > qpWave version: 1520
> >
> > *** recommended that inbreed be explicitly set ***
> > inbreed set YES
> > tmp: /tmp/fsx.7302
> > sh: 1: qpfstats: not found
> > bad open /tmp/fsx.7302
> > (openit) can't open file /tmp/fsx.7302 of type r
> > error info: No such file or directory
> > Segmentation fault (core dumped)
> >
> > What's wrong with it?
> >
> > —
> > Reply to this email directly, view it on GitHub, or unsubscribe.
> > You are receiving this because you are subscribed to this thread.
>
> —
> Reply to this email directly, view it on GitHub
> <
#92 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AUI4QZQWK7P4OEGANJRMLU3VQHAMVANCNFSM5ZMKI2OQ
>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEE77BYFS546NSUYJUB5A4LVQJB27ANCNFSM5ZMKI2OQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Dear Nick
Thank you very much for your reply
I can see the message like this
Maybe I guess that I should designate the absolute path in the qpWave code,
but how can I fix it? Maybe the qpWave program is written by binary language
- Jonghyun Kim -
[image: image.png]
2022년 6월 22일 (수) 오전 8:11, bumblenick ***@***.***>님이 작성:
… Before you run qpWave please just run qpfstats (no parameters)
You should see something like:
no parameters
## qpfstats version: 735
but I suspect you will get qpfstats: command not found
On Tue, Jun 21, 2022 at 6:54 PM Jonghyun Kim ***@***.***>
wrote:
> Dear Nick
>
> Hello, Thank you for your reply
> But, I actually have the qpfstats file, but why the program cannot find
> qpfstats?
> What should I do? Is there any problem in my files?
>
> - Jonghyun Kim -
>
> [image: image.png]
>
> 2022년 6월 21일 (화) 오후 10:36, bumblenick ***@***.***>님이 작성:
>
> > qpAdm calls qpfstats which must be in your path
> > The key error line in your output is
> > qpfstats not found
> >
> > Nick
> >
> >
> > Sent from my iPhone
> >
> > > On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
> > >
> > >
> > > Hello,
> > > When I run qpWave in AdmixTools, I met a error: segmentation fault
> (core
> > dumped)
> > > Here is the error message
> > >
> > > qpWave version: 1520
> > >
> > > *** recommended that inbreed be explicitly set ***
> > > inbreed set YES
> > > tmp: /tmp/fsx.7302
> > > sh: 1: qpfstats: not found
> > > bad open /tmp/fsx.7302
> > > (openit) can't open file /tmp/fsx.7302 of type r
> > > error info: No such file or directory
> > > Segmentation fault (core dumped)
> > >
> > > What's wrong with it?
> > >
> > > —
> > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > You are receiving this because you are subscribed to this thread.
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#92 (comment)
> >,
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AUI4QZQWK7P4OEGANJRMLU3VQHAMVANCNFSM5ZMKI2OQ
> >
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#92 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AEE77BYFS546NSUYJUB5A4LVQJB27ANCNFSM5ZMKI2OQ
>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUI4QZSJSE3BNWVB4GZYJX3VQJD2RANCNFSM5ZMKI2OQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
If you wish to modify the code there is a line:
sprintf(sss, "qpfstats -p %s > %s", ppp, fslog) ;
You can change qpfstats to an absolute path and recompile
Good luck!
N
On Tue, Jun 21, 2022 at 7:35 PM Jonghyun Kim ***@***.***>
wrote:
… Dear Nick
Thank you very much for your reply
I can see the message like this
Maybe I guess that I should designate the absolute path in the qpWave code,
but how can I fix it? Maybe the qpWave program is written by binary
language
- Jonghyun Kim -
[image: image.png]
2022년 6월 22일 (수) 오전 8:11, bumblenick ***@***.***>님이 작성:
> Before you run qpWave please just run qpfstats (no parameters)
> You should see something like:
> no parameters
> ## qpfstats version: 735
>
> but I suspect you will get qpfstats: command not found
>
>
>
> On Tue, Jun 21, 2022 at 6:54 PM Jonghyun Kim ***@***.***>
> wrote:
>
> > Dear Nick
> >
> > Hello, Thank you for your reply
> > But, I actually have the qpfstats file, but why the program cannot find
> > qpfstats?
> > What should I do? Is there any problem in my files?
> >
> > - Jonghyun Kim -
> >
> > [image: image.png]
> >
> > 2022년 6월 21일 (화) 오후 10:36, bumblenick ***@***.***>님이 작성:
> >
> > > qpAdm calls qpfstats which must be in your path
> > > The key error line in your output is
> > > qpfstats not found
> > >
> > > Nick
> > >
> > >
> > > Sent from my iPhone
> > >
> > > > On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
> > > >
> > > >
> > > > Hello,
> > > > When I run qpWave in AdmixTools, I met a error: segmentation fault
> > (core
> > > dumped)
> > > > Here is the error message
> > > >
> > > > qpWave version: 1520
> > > >
> > > > *** recommended that inbreed be explicitly set ***
> > > > inbreed set YES
> > > > tmp: /tmp/fsx.7302
> > > > sh: 1: qpfstats: not found
> > > > bad open /tmp/fsx.7302
> > > > (openit) can't open file /tmp/fsx.7302 of type r
> > > > error info: No such file or directory
> > > > Segmentation fault (core dumped)
> > > >
> > > > What's wrong with it?
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > > You are receiving this because you are subscribed to this thread.
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> >
>
#92 (comment)
> > >,
> > > or unsubscribe
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/AUI4QZQWK7P4OEGANJRMLU3VQHAMVANCNFSM5ZMKI2OQ
> > >
> > > .
> > > You are receiving this because you authored the thread.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#92 (comment)
> >,
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AEE77BYFS546NSUYJUB5A4LVQJB27ANCNFSM5ZMKI2OQ
> >
> > .
> > You are receiving this because you commented.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#92 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AUI4QZSJSE3BNWVB4GZYJX3VQJD2RANCNFSM5ZMKI2OQ
>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEE77B4RIVGYTHFBRK7C3ELVQJGT7ANCNFSM5ZMKI2OQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Dear Nick
I'm sorry for asking a lot of questions, but,
I meant that "How can I fix the code although qpWave program is written by
binary language"
sorry for asking a lot
…-Jonghyun Kim-
[image: image.png]
2022년 6월 22일 (수) 오전 8:45, bumblenick ***@***.***>님이 작성:
If you wish to modify the code there is a line:
sprintf(sss, "qpfstats -p %s > %s", ppp, fslog) ;
You can change qpfstats to an absolute path and recompile
Good luck!
N
On Tue, Jun 21, 2022 at 7:35 PM Jonghyun Kim ***@***.***>
wrote:
> Dear Nick
>
> Thank you very much for your reply
> I can see the message like this
> Maybe I guess that I should designate the absolute path in the qpWave
code,
> but how can I fix it? Maybe the qpWave program is written by binary
> language
>
> - Jonghyun Kim -
>
> [image: image.png]
>
>
>
> 2022년 6월 22일 (수) 오전 8:11, bumblenick ***@***.***>님이 작성:
>
> > Before you run qpWave please just run qpfstats (no parameters)
> > You should see something like:
> > no parameters
> > ## qpfstats version: 735
> >
> > but I suspect you will get qpfstats: command not found
> >
> >
> >
> > On Tue, Jun 21, 2022 at 6:54 PM Jonghyun Kim ***@***.***>
> > wrote:
> >
> > > Dear Nick
> > >
> > > Hello, Thank you for your reply
> > > But, I actually have the qpfstats file, but why the program cannot
find
> > > qpfstats?
> > > What should I do? Is there any problem in my files?
> > >
> > > - Jonghyun Kim -
> > >
> > > [image: image.png]
> > >
> > > 2022년 6월 21일 (화) 오후 10:36, bumblenick ***@***.***>님이 작성:
> > >
> > > > qpAdm calls qpfstats which must be in your path
> > > > The key error line in your output is
> > > > qpfstats not found
> > > >
> > > > Nick
> > > >
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
> > > > >
> > > > >
> > > > > Hello,
> > > > > When I run qpWave in AdmixTools, I met a error: segmentation
fault
> > > (core
> > > > dumped)
> > > > > Here is the error message
> > > > >
> > > > > qpWave version: 1520
> > > > >
> > > > > *** recommended that inbreed be explicitly set ***
> > > > > inbreed set YES
> > > > > tmp: /tmp/fsx.7302
> > > > > sh: 1: qpfstats: not found
> > > > > bad open /tmp/fsx.7302
> > > > > (openit) can't open file /tmp/fsx.7302 of type r
> > > > > error info: No such file or directory
> > > > > Segmentation fault (core dumped)
> > > > >
> > > > > What's wrong with it?
> > > > >
> > > > > —
> > > > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > > > You are receiving this because you are subscribed to this thread.
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub
> > > > <
> > >
> >
>
#92 (comment)
> > > >,
> > > > or unsubscribe
> > > > <
> > >
> >
>
https://github.com/notifications/unsubscribe-auth/AUI4QZQWK7P4OEGANJRMLU3VQHAMVANCNFSM5ZMKI2OQ
> > > >
> > > > .
> > > > You are receiving this because you authored the thread.Message ID:
> > > > ***@***.***>
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> >
>
#92 (comment)
> > >,
> > > or unsubscribe
> > > <
> >
>
https://github.com/notifications/unsubscribe-auth/AEE77BYFS546NSUYJUB5A4LVQJB27ANCNFSM5ZMKI2OQ
> > >
> > > .
> > > You are receiving this because you commented.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
>
#92 (comment)
> >,
> > or unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AUI4QZSJSE3BNWVB4GZYJX3VQJD2RANCNFSM5ZMKI2OQ
> >
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <
#92 (comment)
>,
> or unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AEE77B4RIVGYTHFBRK7C3ELVQJGT7ANCNFSM5ZMKI2OQ
>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUI4QZR3ZXYJCRCCWSXSTFLVQJHX7ANCNFSM5ZMKI2OQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
I think I have run out of help
Please talk to a sysadmin at this point
N
…Sent from my iPhone
On Jun 21, 2022, at 9:24 PM, Jonghyun Kim ***@***.***> wrote:
Dear Nick
I'm sorry for asking a lot of questions, but,
I meant that "How can I fix the code although qpWave program is written by
binary language"
sorry for asking a lot
-Jonghyun Kim-
[image: image.png]
2022년 6월 22일 (수) 오전 8:45, bumblenick ***@***.***>님이 작성:
> If you wish to modify the code there is a line:
> sprintf(sss, "qpfstats -p %s > %s", ppp, fslog) ;
> You can change qpfstats to an absolute path and recompile
>
> Good luck!
>
> N
>
>
> On Tue, Jun 21, 2022 at 7:35 PM Jonghyun Kim ***@***.***>
> wrote:
>
> > Dear Nick
> >
> > Thank you very much for your reply
> > I can see the message like this
> > Maybe I guess that I should designate the absolute path in the qpWave
> code,
> > but how can I fix it? Maybe the qpWave program is written by binary
> > language
> >
> > - Jonghyun Kim -
> >
> > [image: image.png]
> >
> >
> >
> > 2022년 6월 22일 (수) 오전 8:11, bumblenick ***@***.***>님이 작성:
> >
> > > Before you run qpWave please just run qpfstats (no parameters)
> > > You should see something like:
> > > no parameters
> > > ## qpfstats version: 735
> > >
> > > but I suspect you will get qpfstats: command not found
> > >
> > >
> > >
> > > On Tue, Jun 21, 2022 at 6:54 PM Jonghyun Kim ***@***.***>
> > > wrote:
> > >
> > > > Dear Nick
> > > >
> > > > Hello, Thank you for your reply
> > > > But, I actually have the qpfstats file, but why the program cannot
> find
> > > > qpfstats?
> > > > What should I do? Is there any problem in my files?
> > > >
> > > > - Jonghyun Kim -
> > > >
> > > > [image: image.png]
> > > >
> > > > 2022년 6월 21일 (화) 오후 10:36, bumblenick ***@***.***>님이 작성:
> > > >
> > > > > qpAdm calls qpfstats which must be in your path
> > > > > The key error line in your output is
> > > > > qpfstats not found
> > > > >
> > > > > Nick
> > > > >
> > > > >
> > > > > Sent from my iPhone
> > > > >
> > > > > > On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
> > > > > >
> > > > > >
> > > > > > Hello,
> > > > > > When I run qpWave in AdmixTools, I met a error: segmentation
> fault
> > > > (core
> > > > > dumped)
> > > > > > Here is the error message
> > > > > >
> > > > > > qpWave version: 1520
> > > > > >
> > > > > > *** recommended that inbreed be explicitly set ***
> > > > > > inbreed set YES
> > > > > > tmp: /tmp/fsx.7302
> > > > > > sh: 1: qpfstats: not found
> > > > > > bad open /tmp/fsx.7302
> > > > > > (openit) can't open file /tmp/fsx.7302 of type r
> > > > > > error info: No such file or directory
> > > > > > Segmentation fault (core dumped)
> > > > > >
> > > > > > What's wrong with it?
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly, view it on GitHub, or unsubscribe.
> > > > > > You are receiving this because you are subscribed to this thread.
> > > > >
> > > > > —
> > > > > Reply to this email directly, view it on GitHub
> > > > > <
> > > >
> > >
> >
> #92 (comment)
> > > > >,
> > > > > or unsubscribe
> > > > > <
> > > >
> > >
> >
> https://github.com/notifications/unsubscribe-auth/AUI4QZQWK7P4OEGANJRMLU3VQHAMVANCNFSM5ZMKI2OQ
> > > > >
> > > > > .
> > > > > You are receiving this because you authored the thread.Message ID:
> > > > > ***@***.***>
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub
> > > > <
> > >
> >
> #92 (comment)
> > > >,
> > > > or unsubscribe
> > > > <
> > >
> >
> https://github.com/notifications/unsubscribe-auth/AEE77BYFS546NSUYJUB5A4LVQJB27ANCNFSM5ZMKI2OQ
> > > >
> > > > .
> > > > You are receiving this because you commented.Message ID:
> > > > ***@***.***>
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> >
> #92 (comment)
> > >,
> > > or unsubscribe
> > > <
> >
> https://github.com/notifications/unsubscribe-auth/AUI4QZSJSE3BNWVB4GZYJX3VQJD2RANCNFSM5ZMKI2OQ
> > >
> > > .
> > > You are receiving this because you authored the thread.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
> #92 (comment)
> >,
> > or unsubscribe
> > <
> https://github.com/notifications/unsubscribe-auth/AEE77B4RIVGYTHFBRK7C3ELVQJGT7ANCNFSM5ZMKI2OQ
> >
> > .
> > You are receiving this because you commented.Message ID:
> > ***@***.***>
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#92 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AUI4QZR3ZXYJCRCCWSXSTFLVQJHX7ANCNFSM5ZMKI2OQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
|
Dear Nick
I'm sorry, but can I ask one more question?
I set the alias qpfstats="~~~/bin/qpfstats" and I could get the message
even though I did not write the full absolute path
[image: image.png]
But, my qpWave and qpAdm program don't still work because they cannot find
qpfstats
[image: image.png]
What should I do? I cannot find what is wrong with it.
I'm sorry for asking a lot of questions, but could you help me?
…-Jonghyun Kim-
2022년 6월 22일 (수) 오전 11:47, bumblenick ***@***.***>님이 작성:
I think I have run out of help
Please talk to a sysadmin at this point
N
Sent from my iPhone
> On Jun 21, 2022, at 9:24 PM, Jonghyun Kim ***@***.***> wrote:
>
>
> Dear Nick
>
> I'm sorry for asking a lot of questions, but,
> I meant that "How can I fix the code although qpWave program is written
by
> binary language"
> sorry for asking a lot
>
> -Jonghyun Kim-
> [image: image.png]
>
> 2022년 6월 22일 (수) 오전 8:45, bumblenick ***@***.***>님이 작성:
>
> > If you wish to modify the code there is a line:
> > sprintf(sss, "qpfstats -p %s > %s", ppp, fslog) ;
> > You can change qpfstats to an absolute path and recompile
> >
> > Good luck!
> >
> > N
> >
> >
> > On Tue, Jun 21, 2022 at 7:35 PM Jonghyun Kim ***@***.***>
> > wrote:
> >
> > > Dear Nick
> > >
> > > Thank you very much for your reply
> > > I can see the message like this
> > > Maybe I guess that I should designate the absolute path in the qpWave
> > code,
> > > but how can I fix it? Maybe the qpWave program is written by binary
> > > language
> > >
> > > - Jonghyun Kim -
> > >
> > > [image: image.png]
> > >
> > >
> > >
> > > 2022년 6월 22일 (수) 오전 8:11, bumblenick ***@***.***>님이 작성:
> > >
> > > > Before you run qpWave please just run qpfstats (no parameters)
> > > > You should see something like:
> > > > no parameters
> > > > ## qpfstats version: 735
> > > >
> > > > but I suspect you will get qpfstats: command not found
> > > >
> > > >
> > > >
> > > > On Tue, Jun 21, 2022 at 6:54 PM Jonghyun Kim ***@***.***>
> > > > wrote:
> > > >
> > > > > Dear Nick
> > > > >
> > > > > Hello, Thank you for your reply
> > > > > But, I actually have the qpfstats file, but why the program
cannot
> > find
> > > > > qpfstats?
> > > > > What should I do? Is there any problem in my files?
> > > > >
> > > > > - Jonghyun Kim -
> > > > >
> > > > > [image: image.png]
> > > > >
> > > > > 2022년 6월 21일 (화) 오후 10:36, bumblenick ***@***.***>님이 작성:
> > > > >
> > > > > > qpAdm calls qpfstats which must be in your path
> > > > > > The key error line in your output is
> > > > > > qpfstats not found
> > > > > >
> > > > > > Nick
> > > > > >
> > > > > >
> > > > > > Sent from my iPhone
> > > > > >
> > > > > > > On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
> > > > > > >
> > > > > > >
> > > > > > > Hello,
> > > > > > > When I run qpWave in AdmixTools, I met a error: segmentation
> > fault
> > > > > (core
> > > > > > dumped)
> > > > > > > Here is the error message
> > > > > > >
> > > > > > > qpWave version: 1520
> > > > > > >
> > > > > > > *** recommended that inbreed be explicitly set ***
> > > > > > > inbreed set YES
> > > > > > > tmp: /tmp/fsx.7302
> > > > > > > sh: 1: qpfstats: not found
> > > > > > > bad open /tmp/fsx.7302
> > > > > > > (openit) can't open file /tmp/fsx.7302 of type r
> > > > > > > error info: No such file or directory
> > > > > > > Segmentation fault (core dumped)
> > > > > > >
> > > > > > > What's wrong with it?
> > > > > > >
> > > > > > > —
> > > > > > > Reply to this email directly, view it on GitHub, or
unsubscribe.
> > > > > > > You are receiving this because you are subscribed to this
thread.
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly, view it on GitHub
> > > > > > <
> > > > >
> > > >
> > >
> >
#92 (comment)
> > > > > >,
> > > > > > or unsubscribe
> > > > > > <
> > > > >
> > > >
> > >
> >
https://github.com/notifications/unsubscribe-auth/AUI4QZQWK7P4OEGANJRMLU3VQHAMVANCNFSM5ZMKI2OQ
> > > > > >
> > > > > > .
> > > > > > You are receiving this because you authored the thread.Message
ID:
> > > > > > ***@***.***>
> > > > > >
> > > > >
> > > > > —
> > > > > Reply to this email directly, view it on GitHub
> > > > > <
> > > >
> > >
> >
#92 (comment)
> > > > >,
> > > > > or unsubscribe
> > > > > <
> > > >
> > >
> >
https://github.com/notifications/unsubscribe-auth/AEE77BYFS546NSUYJUB5A4LVQJB27ANCNFSM5ZMKI2OQ
> > > > >
> > > > > .
> > > > > You are receiving this because you commented.Message ID:
> > > > > ***@***.***>
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub
> > > > <
> > >
> >
#92 (comment)
> > > >,
> > > > or unsubscribe
> > > > <
> > >
> >
https://github.com/notifications/unsubscribe-auth/AUI4QZSJSE3BNWVB4GZYJX3VQJD2RANCNFSM5ZMKI2OQ
> > > >
> > > > .
> > > > You are receiving this because you authored the thread.Message ID:
> > > > ***@***.***>
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> >
#92 (comment)
> > >,
> > > or unsubscribe
> > > <
> >
https://github.com/notifications/unsubscribe-auth/AEE77B4RIVGYTHFBRK7C3ELVQJGT7ANCNFSM5ZMKI2OQ
> > >
> > > .
> > > You are receiving this because you commented.Message ID:
> > > ***@***.***>
> > >
> >
> > —
> > Reply to this email directly, view it on GitHub
> > <
#92 (comment)
>,
> > or unsubscribe
> > <
https://github.com/notifications/unsubscribe-auth/AUI4QZR3ZXYJCRCCWSXSTFLVQJHX7ANCNFSM5ZMKI2OQ
>
> > .
> > You are receiving this because you authored the thread.Message ID:
> > ***@***.***>
> >
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you commented.
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUI4QZT57RQ6P2JD7T3QS6DVQJ5DBANCNFSM5ZMKI2OQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
You need sysadmin help
N
…Sent from my iPhone
On Jun 22, 2022, at 10:16 PM, Jonghyun Kim ***@***.***> wrote:
Dear Nick
I'm sorry, but can I ask one more question?
I set the alias qpfstats="~~~/bin/qpfstats" and I could get the message
even though I did not write the full absolute path
[image: image.png]
But, my qpWave and qpAdm program don't still work because they cannot find
qpfstats
[image: image.png]
What should I do? I cannot find what is wrong with it.
I'm sorry for asking a lot of questions, but could you help me?
-Jonghyun Kim-
2022년 6월 22일 (수) 오전 11:47, bumblenick ***@***.***>님이 작성:
> I think I have run out of help
> Please talk to a sysadmin at this point
>
> N
>
> Sent from my iPhone
>
> > On Jun 21, 2022, at 9:24 PM, Jonghyun Kim ***@***.***> wrote:
> >
> >
> > Dear Nick
> >
> > I'm sorry for asking a lot of questions, but,
> > I meant that "How can I fix the code although qpWave program is written
> by
> > binary language"
> > sorry for asking a lot
> >
> > -Jonghyun Kim-
> > [image: image.png]
> >
> > 2022년 6월 22일 (수) 오전 8:45, bumblenick ***@***.***>님이 작성:
> >
> > > If you wish to modify the code there is a line:
> > > sprintf(sss, "qpfstats -p %s > %s", ppp, fslog) ;
> > > You can change qpfstats to an absolute path and recompile
> > >
> > > Good luck!
> > >
> > > N
> > >
> > >
> > > On Tue, Jun 21, 2022 at 7:35 PM Jonghyun Kim ***@***.***>
> > > wrote:
> > >
> > > > Dear Nick
> > > >
> > > > Thank you very much for your reply
> > > > I can see the message like this
> > > > Maybe I guess that I should designate the absolute path in the qpWave
> > > code,
> > > > but how can I fix it? Maybe the qpWave program is written by binary
> > > > language
> > > >
> > > > - Jonghyun Kim -
> > > >
> > > > [image: image.png]
> > > >
> > > >
> > > >
> > > > 2022년 6월 22일 (수) 오전 8:11, bumblenick ***@***.***>님이 작성:
> > > >
> > > > > Before you run qpWave please just run qpfstats (no parameters)
> > > > > You should see something like:
> > > > > no parameters
> > > > > ## qpfstats version: 735
> > > > >
> > > > > but I suspect you will get qpfstats: command not found
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Jun 21, 2022 at 6:54 PM Jonghyun Kim ***@***.***>
> > > > > wrote:
> > > > >
> > > > > > Dear Nick
> > > > > >
> > > > > > Hello, Thank you for your reply
> > > > > > But, I actually have the qpfstats file, but why the program
> cannot
> > > find
> > > > > > qpfstats?
> > > > > > What should I do? Is there any problem in my files?
> > > > > >
> > > > > > - Jonghyun Kim -
> > > > > >
> > > > > > [image: image.png]
> > > > > >
> > > > > > 2022년 6월 21일 (화) 오후 10:36, bumblenick ***@***.***>님이 작성:
> > > > > >
> > > > > > > qpAdm calls qpfstats which must be in your path
> > > > > > > The key error line in your output is
> > > > > > > qpfstats not found
> > > > > > >
> > > > > > > Nick
> > > > > > >
> > > > > > >
> > > > > > > Sent from my iPhone
> > > > > > >
> > > > > > > > On Jun 21, 2022, at 9:19 AM, Jonghyun Kim ***@***.***> wrote:
> > > > > > > >
> > > > > > > >
> > > > > > > > Hello,
> > > > > > > > When I run qpWave in AdmixTools, I met a error: segmentation
> > > fault
> > > > > > (core
> > > > > > > dumped)
> > > > > > > > Here is the error message
> > > > > > > >
> > > > > > > > qpWave version: 1520
> > > > > > > >
> > > > > > > > *** recommended that inbreed be explicitly set ***
> > > > > > > > inbreed set YES
> > > > > > > > tmp: /tmp/fsx.7302
> > > > > > > > sh: 1: qpfstats: not found
> > > > > > > > bad open /tmp/fsx.7302
> > > > > > > > (openit) can't open file /tmp/fsx.7302 of type r
> > > > > > > > error info: No such file or directory
> > > > > > > > Segmentation fault (core dumped)
> > > > > > > >
> > > > > > > > What's wrong with it?
> > > > > > > >
> > > > > > > > —
> > > > > > > > Reply to this email directly, view it on GitHub, or
> unsubscribe.
> > > > > > > > You are receiving this because you are subscribed to this
> thread.
> > > > > > >
> > > > > > > —
> > > > > > > Reply to this email directly, view it on GitHub
> > > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> #92 (comment)
> > > > > > >,
> > > > > > > or unsubscribe
> > > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> https://github.com/notifications/unsubscribe-auth/AUI4QZQWK7P4OEGANJRMLU3VQHAMVANCNFSM5ZMKI2OQ
> > > > > > >
> > > > > > > .
> > > > > > > You are receiving this because you authored the thread.Message
> ID:
> > > > > > > ***@***.***>
> > > > > > >
> > > > > >
> > > > > > —
> > > > > > Reply to this email directly, view it on GitHub
> > > > > > <
> > > > >
> > > >
> > >
> #92 (comment)
> > > > > >,
> > > > > > or unsubscribe
> > > > > > <
> > > > >
> > > >
> > >
> https://github.com/notifications/unsubscribe-auth/AEE77BYFS546NSUYJUB5A4LVQJB27ANCNFSM5ZMKI2OQ
> > > > > >
> > > > > > .
> > > > > > You are receiving this because you commented.Message ID:
> > > > > > ***@***.***>
> > > > > >
> > > > >
> > > > > —
> > > > > Reply to this email directly, view it on GitHub
> > > > > <
> > > >
> > >
> #92 (comment)
> > > > >,
> > > > > or unsubscribe
> > > > > <
> > > >
> > >
> https://github.com/notifications/unsubscribe-auth/AUI4QZSJSE3BNWVB4GZYJX3VQJD2RANCNFSM5ZMKI2OQ
> > > > >
> > > > > .
> > > > > You are receiving this because you authored the thread.Message ID:
> > > > > ***@***.***>
> > > > >
> > > >
> > > > —
> > > > Reply to this email directly, view it on GitHub
> > > > <
> > >
> #92 (comment)
> > > >,
> > > > or unsubscribe
> > > > <
> > >
> https://github.com/notifications/unsubscribe-auth/AEE77B4RIVGYTHFBRK7C3ELVQJGT7ANCNFSM5ZMKI2OQ
> > > >
> > > > .
> > > > You are receiving this because you commented.Message ID:
> > > > ***@***.***>
> > > >
> > >
> > > —
> > > Reply to this email directly, view it on GitHub
> > > <
> #92 (comment)
> >,
> > > or unsubscribe
> > > <
> https://github.com/notifications/unsubscribe-auth/AUI4QZR3ZXYJCRCCWSXSTFLVQJHX7ANCNFSM5ZMKI2OQ
> >
> > > .
> > > You are receiving this because you authored the thread.Message ID:
> > > ***@***.***>
> > >
> > —
> > Reply to this email directly, view it on GitHub, or unsubscribe.
> > You are receiving this because you commented.
>
> —
> Reply to this email directly, view it on GitHub
> <#92 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AUI4QZT57RQ6P2JD7T3QS6DVQJ5DBANCNFSM5ZMKI2OQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
When I run qpWave in AdmixTools, I met a error: segmentation fault (core dumped)
Here is the error message
qpWave version: 1520
*** recommended that inbreed be explicitly set ***
inbreed set YES
tmp: /tmp/fsx.7302
sh: 1: qpfstats: not found
bad open /tmp/fsx.7302
(openit) can't open file /tmp/fsx.7302 of type r
error info: No such file or directory
Segmentation fault (core dumped)
What's wrong with it?
The text was updated successfully, but these errors were encountered: