question about segmentation fault - Linux

This is a discussion on question about segmentation fault - Linux ; I hope this is the right newsgroup to pose my question. I cannot figure out the main reason why "segmentation fault" goes out. Therefore I'm seeking such an assistance. ------------------------------------------------------------------ Running tar 1.14, it gives "segmentation fault" Running tar 1.13 ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: question about segmentation fault

  1. question about segmentation fault

    I hope this is the right newsgroup to pose my question.

    I cannot figure out the main reason why "segmentation fault"
    goes out. Therefore I'm seeking such an assistance.

    ------------------------------------------------------------------
    Running tar 1.14, it gives "segmentation fault"
    Running tar 1.13 all works fine.

    I'd like to understand why, or at least to get some clue.

    ldd tar-1.14
    librt.so.1 => /lib/librt.so.1 (0x40035000)
    libc.so.6 => /lib/libc.so.6 (0x40048000)
    libpthread.so.0 => /lib/libpthread.so.0 (0x40166000)
    /lib/ld-linux.so.2 (0x40000000)

    ldd tar-1.13
    libc.so.6 => /lib/libc.so.6 (0x40035000)
    /lib/ld-linux.so.2 (0x40000000)

    --------------------------------------------------------------
    I guess that answer could give me some hint to
    understand why also:
    firefox
    rc.syslog

    give me an "segmentation fault" message.

    THX,
    GB

  2. Re: question about segmentation fault

    Hmm.. normally, a segfault indicates that there's something wrong
    allocating memory.
    You could try starting a segfaulting app in GDB, and give a 'bt' after
    it segfaults to see a backtrace.

    Judging from the fact tar 1.13 works fine, and 1.14 does not, one would
    assume it's either in librt or libpthread.
    Since firefox also uses both, I can't be sure which of them is the
    culprit. But you could try reinstalling both libraries.

    All in all, a system that segfaults on one of those libs could be very
    messed up, best backup while you still have a prompt.

    regards,

    -R-

    Giancarlo Bassi wrote:
    > I hope this is the right newsgroup to pose my question.
    >
    > I cannot figure out the main reason why "segmentation fault"
    > goes out. Therefore I'm seeking such an assistance.
    >
    > ------------------------------------------------------------------
    > Running tar 1.14, it gives "segmentation fault"
    > Running tar 1.13 all works fine.
    >
    > I'd like to understand why, or at least to get some clue.
    >
    > ldd tar-1.14
    > librt.so.1 => /lib/librt.so.1 (0x40035000)
    > libc.so.6 => /lib/libc.so.6 (0x40048000)
    > libpthread.so.0 => /lib/libpthread.so.0 (0x40166000)
    > /lib/ld-linux.so.2 (0x40000000)
    >
    > ldd tar-1.13
    > libc.so.6 => /lib/libc.so.6 (0x40035000)
    > /lib/ld-linux.so.2 (0x40000000)
    >
    > --------------------------------------------------------------
    > I guess that answer could give me some hint to
    > understand why also:
    > firefox
    > rc.syslog
    >
    > give me an "segmentation fault" message.
    >
    > THX,
    > GB


  3. Re: question about segmentation fault

    Hmm.. normally, a segfault indicates that there's something wrong
    allocating memory.
    You could try starting a segfaulting app in GDB, and give a 'bt' after
    it segfaults to see a backtrace.

    Judging from the fact tar 1.13 works fine, and 1.14 does not, one would
    assume it's either in librt or libpthread.
    Since firefox also uses both, I can't be sure which of them is the
    culprit. But you could try reinstalling both libraries.

    All in all, a system that segfaults on one of those libs could be very
    messed up, best backup while you still have a prompt.

    regards,

    -R-

    Ps: sorry if this is a double post. Not sure if the first one went out ok.

    Giancarlo Bassi wrote:
    > I hope this is the right newsgroup to pose my question.
    >
    > I cannot figure out the main reason why "segmentation fault"
    > goes out. Therefore I'm seeking such an assistance.
    >
    > ------------------------------------------------------------------
    > Running tar 1.14, it gives "segmentation fault"
    > Running tar 1.13 all works fine.
    >
    > I'd like to understand why, or at least to get some clue.
    >
    > ldd tar-1.14
    > librt.so.1 => /lib/librt.so.1 (0x40035000)
    > libc.so.6 => /lib/libc.so.6 (0x40048000)
    > libpthread.so.0 => /lib/libpthread.so.0 (0x40166000)
    > /lib/ld-linux.so.2 (0x40000000)
    >
    > ldd tar-1.13
    > libc.so.6 => /lib/libc.so.6 (0x40035000)
    > /lib/ld-linux.so.2 (0x40000000)
    >
    > --------------------------------------------------------------
    > I guess that answer could give me some hint to
    > understand why also:
    > firefox
    > rc.syslog
    >
    > give me an "segmentation fault" message.
    >
    > THX,
    > GB


  4. Re: question about segmentation fault

    Right, it was matter of those two libraries.
    I made some mess with erroneous updating of glibc-solibs
    (under slackware). Now I fixed successfully.
    Thanks a lot,
    -- GB


    On Tue, 23 Oct 2007, Jurgen Haan wrote:

    > Hmm.. normally, a segfault indicates that there's something wrong
    > allocating memory.
    > You could try starting a segfaulting app in GDB, and give a 'bt' after
    > it segfaults to see a backtrace.
    >
    > Judging from the fact tar 1.13 works fine, and 1.14 does not, one would
    > assume it's either in librt or libpthread.
    > Since firefox also uses both, I can't be sure which of them is the
    > culprit. But you could try reinstalling both libraries.
    >
    > All in all, a system that segfaults on one of those libs could be very
    > messed up, best backup while you still have a prompt.
    >
    > regards,
    >
    > -R-
    >
    > Ps: sorry if this is a double post. Not sure if the first one went out ok.
    >
    > Giancarlo Bassi wrote:
    >> I hope this is the right newsgroup to pose my question.
    >>
    >> I cannot figure out the main reason why "segmentation fault"
    >> goes out. Therefore I'm seeking such an assistance.
    >>
    >> ------------------------------------------------------------------
    >> Running tar 1.14, it gives "segmentation fault"
    >> Running tar 1.13 all works fine.
    >>
    >> I'd like to understand why, or at least to get some clue.
    >>
    >> ldd tar-1.14
    >> librt.so.1 => /lib/librt.so.1 (0x40035000)
    >> libc.so.6 => /lib/libc.so.6 (0x40048000)
    >> libpthread.so.0 => /lib/libpthread.so.0 (0x40166000)
    >> /lib/ld-linux.so.2 (0x40000000)
    >>
    >> ldd tar-1.13
    >> libc.so.6 => /lib/libc.so.6 (0x40035000)
    >> /lib/ld-linux.so.2 (0x40000000)
    >>
    >> --------------------------------------------------------------
    >> I guess that answer could give me some hint to
    >> understand why also:
    >> firefox
    >> rc.syslog
    >>
    >> give me an "segmentation fault" message.
    >>
    >> THX,
    >> GB

    >


+ Reply to Thread