Home > Segfault Error > Segfault Error 4 In Ld 2.13 So

Segfault Error 4 In Ld 2.13 So

landysaccount View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by landysaccount 01-14-2009, 02:27 PM #8 landysaccount Member Registered: Sep 2008 Location: Dominican Tinkster View Public Profile View LQ Blog View Review Entries View HCL Entries View LQ Wiki Contributions Find More Posts by Tinkster View Blog 01-15-2009, 05:50 PM #12 landysaccount Member Jul 21:40 libanl-2.14.so lrwxrwxrwx 1 root root 14 30. All others work fine. Check This Out

I've seen segfaults as an indicator for both a buggy/dieing chip-set, and for dieing RAMs. Marlino View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Marlino 08-02-2011, 04:25 AM #12 Aky^ LQ Newbie Registered: Jul 2011 Distribution: What else might be causing this problem? forever, now the powers that be have > decided to clamp down hard, hence the filtered/moderated posts that we > all know about and which cannot be denied as it has website here

Should they be set to AHCI > instead? (third option is RAID). Server: zapp OSDir.com debian-user-debian Subject: Re: segfaults and error 4 in ld-2.13.so withsoffice.bin and kate Date Index Thread: Prev Next Thread Index On Sun, 12 Oct 2014, Gary Cheers, Tink Tinkster View Public Profile View LQ Blog View Review Entries View HCL Entries View LQ Wiki Contributions Find More Posts by Tinkster View Blog 01-14-2009, 05:11 PM Bad news, I've just rebuilt with current glibc git head and the problem remains Andrew Benton View Public Profile View LQ Blog View Review Entries View HCL Entries Visit Andrew

Couldn't compile anything that took more than a few minutes w/o a segmentation fault. Now, for the system disabling part: Code: ls -l libc* -rwxr-xr-x 1 root root 8642357 30. I use them daily! Even the test suites run OK.

Trouble? debian-us Don Armstrong 7. 2014-10-12 Re: segfaults and error 4 in ld-2.13.so with soffice. Click Here to receive this Complete Guide absolutely free. look at this web-site That would have been too easy and probably not have been overlooked be the developers, but it seemed worth a try.

I hit the wrong button.}}} In conclusion, I tried re-running the reverse-Depends on libreoffice-common:amd64 but got the usual - 0 packages upgraded, 0 newly installed, 0 to remove and 0 not Would this hint to a solution? I'm tempted to rule out the kernel version as being the problem, as the only kernel header included from aplay.c is something which should be invariant for a given CPU architecture By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.

It happened again. Contact [email protected] Archive: https://lists.debian.org/[email protected] Previous Message by Thread: Re: segfaults and error 4 in ld-2.13.so with soffice.bin and kate On 10/11/2014 06:28 PM, Don Armstrong wrote: On Tue, 07 Oct 2014, I then ran the reverse-Depends as suggested above on kate. If either is yes, investigate there.

Ran memtest86 for a full day w/ no errors. his comment is here If this is happening on a fresh install follow step 4 also1) Make a CrunchBang live USB or CD and get to the boot menu and choose memtest.2)Let memtest run and Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search Both were very random in the way they behaved.My first install must have had similar issues but said it was completed anyway as it DID had alot of errors when trying

Jan 12 23:08:15 trahersa-test -- MARK -- Jan 12 23:28:15 trahersa-test -- MARK -- Jan 12 23:48:15 trahersa-test -- MARK -- Jan 13 00:08:15 trahersa-test -- MARK -- Jan 13 00:28:15 make -C gdb install not to overwrite binutils files) Now, I find gdb has fixed the aplay problem. debian-us Michael Biebl 6. 2014-10-12 Re: segfaults and error 4 in ld-2.13.so with soffice. http://internetmairie.com/segfault-error/segfault-error-6.html hosted at Digital OceanAdvertise on this site 

Jul 16:27 libc.so.6 -> libc-2.14.so This gave me the idea to check whether I would get a different output for the version, if I pointed libc.so.6 to libc-2.13.so. I was able to do other things in the system and tried to login with another putty session but just couldn't. Myself, I would be looking at > kFreeBSD as the next best alternative and if that suffers over this, > then a full migration away from Debian to a direct use

Writer will start but errors out when an attempt is made to open an odt file.

Reason: corrected possibly misleading typing error Marlino View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Marlino 07-29-2011, 07:23 PM #8 Marlino Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search On that note, answer the obvious following questions: 1: Has any software changed? 2: Has any hardware changed? If they still occur, enable coredumps, and get a backtrace of the coredump using gdb or similar. [You'll also want to install all of the -dbg packages you can for the

But I did not strip the debugging symbols yet and could possibly help that way, if someone would be willing to do some serious tutoring with me. ;-) I'm kind of For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. Interested to hear the outcome. navigate here android.

As suggested, I first ran debsum on kate and libreoffice. All check sums were OK. Code: $ whereis gdb gdb: /usr/share/gdb /usr/share/gdb really is a directory. Mitt kontoSökMapsYouTubePlayNyheterGmailDriveKalenderGoogle+ÖversättFotonMerWalletDokumentBloggerKontakterHangoutsÄnnu mer från GoogleLogga inDolda fältSök efter grupper eller meddelanden Search:[]List[]Subjects[]Authors[]Bodies (mustpickalistfirst) Set Page Width: [ 80 ] [ 90 ] [ 100 ] [ 120 ] Viewing messages in

I have tried every program that is installed on my system. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. aplay now works without segfault! Trouble?

But might not work on all systems. Jul 14:22 kbd -rwxr-xr-x 1 root root 671578 30. I'm rather ill prepared / ignorant / inexperienced to investigate such a thing on my own. aplay works: Code: $ gdb aplay ... (gdb) run wasmach.wav Starting program: /usr/bin/aplay wasmach.wav [Thread debugging using libthread_db enabled] Playing WAVE 'wasmach.wav' : Signed 16 bit Little Endian, Rate 22050 Hz,

I just took some "hard way" learning experiences: Compared do_lookup_x in dl-lookup.c of the last few releases of glibc, didn't find a difference there. Marlino View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Marlino 08-04-2011, 06:15 AM #14 Andrew Benton Senior Member Registered: Aug 2003 I was thinking of replacing the HD and the RAM and reinstall debian and see if it will work flawlessly. If you'd like to contribute content, let us know.

Jul 00:41 ld-linux.so.2 -> ld-2.14.so -rwxr-xr-x 1 root root 57244 30. Marlino View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Marlino 07-30-2011, 11:01 AM #9 Marlino LQ Newbie Registered: Jul 2011 Location: I could ping to it and ping to the internet but, I couldn't connect to it. Could boot a Live CD, mount partitions readonly and try to figure out from reading logs if something got installed, de-installed, updated, reconfigured, et cetera recently?

Reason: corrected gcc version Aky^ View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Aky^ 07-26-2011, 04:43 PM #3 Marlino LQ Newbie Proudly powered by Debian.