Re: [LI] Bash core dump

[Raj Mathur <raju@xxxxxxx>]

Since I've never heard of a Bad Bash, I'd presume that the problem is
in your hardware.  Are you overclocking your chip?  Are you using your 
chip to dry eggs on?  Is your memory bad?  Is your cache tainted?

I mean, if shells are going to go and die on us, we may as well be
running winduhs, no?

I'd suggest compiling a kernel and seeing if you get the infamous
Signal11 error.  If you do, it's almost definitely a memory problem.
See the sig11 FAQ to be sure (location of FAQ left as exercise to the
user).

Regards,

- -- Raju

>>>>> "Rutvik" == Rutvik Doshi <hdoshi@xxxxxxxxxxxxxxxx> writes:

    >>  Seems interesting.. One thing, how dya know that bash is the
    >> crook? Did ya do 'gdb -c core' ? One more, where is this core
    >> file created, your home or somewhere else.

    Rutvik> I did gdb -c core and it is created by bash only..moreover
    Rutvik> i also tried running bash under gdb and it did dump a core
    Rutvik> after a segmentation fault....the core file is always
    Rutvik> genertaed in my home directory...
- --------------------------------------------------------------------
For more information on Linux in India visit http://www.linux-india.org/
The Linux India mailing list does not accept postings in HTML format.

------------------------------