Segmentation Fault ( core dumped ) with the command bash

Question

I'm using SUN Solaris-8 and i tried to install an application to run it into : i failed because i got insuffisant disk space. So today i delete some useless thing in the disk but when i try to execute the command bash this message figure out : Segmentation Fault (core dumped).

I read in some forums that's a consequence of a lack of space in the disk or in the memory that's why i got this but i can't fix it .

I also tried the command adb core and i got this :

NT_GWINDOWS currently unsupported note segment entry. core file = core -- program ``bash'' on platform SUNW,Sun-Blade-1500 SIGSEGV: Segmentation Fault data address not found

Any idea about that .?

This doesn't seem to be a programming question. I think you'd be better off on [su]. — Siguza, Sep 06 '16 at 10:29
I'm not so sure asking what's causing a process to `SEGV` should be moved - determining the cause can be considered an implicit programming question. What does `pstack core` show? — Andrew Henle, Sep 06 '16 at 12:02
@AndrewHenle it shows too much lines like this ` 000560ac parse_and_execute (8c400, 0, a9cf0, 4, ac750, b0010) + 50c 0005595c ???????? (b5, b0010, 35128, 0, 4, 9) 00055b04 maybe_execute_file (1, ac750, 1, ae000, ae010, ae010) + 24 000204b8 ???????? (8c400, 8c400, 1, e, 0, 160) 0001fa0c main (8c400, 8c400, 8cc00, 8c400, 0, 0) + 694 0001f360 _start (0, 0, 0, 0, 0, 0) + b8` — Hohenheim, Sep 06 '16 at 12:43
Maybe weren't the useless things you removed that useless? What says `type bash`? — jlliagre, Sep 06 '16 at 17:37
hi @MarkPlotnick i got this `ldd: bash: cannot open file: No such file or directory` — Hohenheim, Sep 07 '16 at 13:21
I got this @jlliagre `libcurses.so.1 => /usr/lib/libcurses.so.1 libsocket.so.1 => /usr/lib/libsocket.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libdl.so.1 => /usr/lib/libdl.so.1 libc.so.1 => /usr/lib/libc.so.1 libmp.so.2 => /usr/lib/libmp.so.2 /usr/platform/SUNW,Sun-Blade-1500/lib/libc_psr.so.1` — Hohenheim, Sep 07 '16 at 13:22
@jlliagre got this : `/usr /usr/bin /usr/bin/bash /usr/share /usr/share/man /usr/share/man/man1 /usr/share/man/man1/bash.1` — Hohenheim, Sep 07 '16 at 13:26
`LD_LIBRARY_PATH=/opt/SUNWspro/lib:/usr/openwin/lib:/opt/sfw/lib:/usr/local/lib` — Hohenheim, Sep 07 '16 at 13:37
but when i launch command `bash` : i got this `Segmentation Fault` . I don't know why — Hohenheim, Sep 07 '16 at 13:59

jlliagre · Accepted Answer · 2016-09-07T14:06:27.890

1

There seems to be an issue with one of the configuration files as bash looks to start properly after disabling them:

bash --noprofile --norc

Alternatively, the LD_LIBRARY_PATH variable might provide incorrect or incompatible libraries, removing it might help too:

unset LD_LIBRARY_PATH

Note, if you are using csh, use unsetenv instead of unset.

edited Sep 07 '16 at 14:06

answered Sep 07 '16 at 13:59

jlliagre

29,783
6
61
72

Thank you so much ! When i use your first command the bash is activated ! but if i'm not using `csh` what is the command replacing `unsetenv` ? – Hohenheim Sep 07 '16 at 14:03
Once an environment variable is unset, it stays unset for the current shell and all its children unless of course it is set again. Under `bash` and other bourne shell compatible shells, you unset a variable with the `unset` command. – jlliagre Sep 07 '16 at 14:05
so to work in `bash ` mode i have to execute this command `bash --noprofile --norc` ? no only `bash` ? – Hohenheim Sep 07 '16 at 14:07
1

If unsetting LD_LIBRARY_PATH doesn't fix the issue, you need to figure out which one of the configuration files is bogus (/etc/profile, ~/.bash_profile , ~/.bashrc, etc.) and fix it. You'd better ask a new question in the right site ( unix.stackexchange.com ) as stackoverflow is for programming questions and shell scripting is not considered a first class citizen here. – jlliagre Sep 07 '16 at 14:12

Segmentation Fault ( core dumped ) with the command bash

1 Answers1