On Wed, Feb 29, 2012 at 7:33 AM, Dave Love d.love-at-liverpool.ac.uk
|gridengine-hoffman| <[email protected]> wrote:
> Michael Hoffman <[email protected]> writes:
>
>> Our system administrators recently upgraded our GridEngine
>> installation to 6.2u5.
>
> [...]
>
>> Now I find that using %s in a qsub command line
>> results in an immediate SIGSEGV.
>
> What happens if it's quoted appropriately for a shell metacharacter
> (presumably with two levels of quoting)?
Sadly, no help.
$ qsub -b y -sync y echo %s
Your job 1639883 ("echo") has been submitted
Job 1639883 exited because of signal SIGSEGV
$ qsub -b y -sync y echo '%s'
Your job 1639884 ("echo") has been submitted
Job 1639884 exited because of signal SIGSEGV
$ qsub -b y -sync y echo '"%s"'
Your job 1639885 ("echo") has been submitted
Job 1639885 exited because of signal SIGSEGV
>> Do you know what causes this?
>
> No, but /var/log/messages should tell you what SEGVed. I'm not sure
> from the output whether it could be the SGE shepherd. I can't reproduce
> it with recent code and tcsh anyhow.
These are the lines that appear to be generated from the output of dmesg:
sge_shepherd[21242]: segfault at 0000000000000001 rip 0000003f73a79b60
rsp 00007fff599b5018 error 4
sge_shepherd[21279]: segfault at 0000000000000001 rip 0000003f73a79b60
rsp 00007fff310cb9e8 error 4
sge_shepherd[21289]: segfault at 0000000000000001 rip 0000003f73a79b60
rsp 00007fffb8c02b88 error 4
Thanks!
--
Michael
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
