Skip to content

Addition of verbose patch for error messages to 0.10.0#2

Merged
bhatiaharsh merged 2 commits intobhatiaharsh:bhatia-splashfrom
FrankD412:flux_patch
Oct 11, 2018
Merged

Addition of verbose patch for error messages to 0.10.0#2
bhatiaharsh merged 2 commits intobhatiaharsh:bhatia-splashfrom
FrankD412:flux_patch

Conversation

@FrankD412
Copy link
Copy Markdown

No description provided.

@bhatiaharsh
Copy link
Copy Markdown
Owner

Frank, can you change the request to merge into "bhatia-splash" ?

@FrankD412 FrankD412 changed the base branch from develop to bhatia-splash October 11, 2018 05:33
@FrankD412
Copy link
Copy Markdown
Author

Oh, good catch. done.

@bhatiaharsh
Copy link
Copy Markdown
Owner

also, i am not sure how spack would apply the patch. we would also somehow need to add this to the package file.

@FrankD412
Copy link
Copy Markdown
Author

Oh, I thought that file was added. I might have readded the same file accidentally. Hold on, I have a change for it.

@bhatiaharsh bhatiaharsh merged commit 3572080 into bhatiaharsh:bhatia-splash Oct 11, 2018
bhatiaharsh pushed a commit that referenced this pull request Jun 10, 2020
* Add OpenMP variant to Umpire

* Initial implementation of Axom package

* Add Axom spack package and fix required dependencies

* Fix overzealous tag replacement

* Attempt to fix version error

* Fix python version attempt #2

* Update raja and umpire

* remove sys_type check

* Address comments in axom package

* Address Greg's comments

* Fix flake8

* more flake8

* Simplify MPIEXEC and MPIEXEC_NUMPROC_FLAG

* Fix typo

* Revert back to slurm check, fix cuda_arch checks

* Fix cuda_arch variant forwarding

* Add cub variant

* Add py-shroud

* Address comments

* Fix shroud path in axom

* Fix merge conflict

* Fix backwards if

* Fix flake8 and add copyright

* format for consistency
bhatiaharsh pushed a commit that referenced this pull request Jun 20, 2020
Whenever attempting to use any ncurses functionality within cscope, a
page fault would result within the ncurses library.

    Program received signal SIGSEGV, Segmentation fault.
    0x00007ffff7fad3cf in termattrs_sp () from .../lib/libncursesw.so.6
    (gdb) bt
    #0  0x00007ffff7fad3cf in termattrs_sp () from .../lib/libncursesw.so.6
    #1  0x00007ffff7faa794 in _nc_setupscreen_sp () from .../lib/libncursesw.so.6
    #2  0x00007ffff7fa614c in newterm_sp () from .../lib/libncursesw.so.6
    #3  0x00007ffff7fa65b9 in newterm () from .../lib/libncursesw.so.6
    #4  0x00007ffff7fa2970 in initscr () from .../lib/libncursesw.so.6
    #5  0x0000000000403dc2 in main (argc=<optimized out>, argv=0x7fffffffcea8) at main.c:574

This is due to a conflict between libtinfo.so and libtinfow.so. Both are
linked into cscope:

    $ ldd $(which cscope)
    /bin/bash: .../lib/libtinfo.so.6: no version information available (required by /bin/bash)
        linux-vdso.so.1 (0x00007fff5dbcb000)
        libncursesw.so.6 => .../lib/libncursesw.so.6 (0x00007f435cc69000)
        libtinfo.so.6 => .../lib/libtinfo.so.6 (0x00007f435cc2c000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f435ca29000)
        libtinfow.so.6 => .../lib/libtinfow.so.6 (0x00007f435c9e8000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f435cca7000)

Specifically linking libtinfow.so instead of libtinfo.so resolves the
issue.

All instances of '...' above represent the path to the installed ncurses
for Spack.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants