Loading ...
Sorry, an error occurred while loading the content.

Re: symbolic link and file-browser

Expand Messages
  • ZarathustraXYZ
    Yes, if I fix the link Me work fine. ... is an ... I ... webservice -
    Message 1 of 11 , May 28, 2007
    • 0 Attachment
      Yes, if I fix the link Me work fine.

      --- In jasspa@yahoogroups.com, Jon Green <jon@...> wrote:
      >
      > ZarathustraXYZ wrote:
      > > Ok, I have found where is the problem.
      > > I didn't realize it before but the link that crash Me
      > > is "strange" :-), this is the output of ls -l:
      > >
      > > lrwxrwxrwx 1 enzo enzo 11 27 mag 00:35 webservice ->
      > > WebService//
      > > drwxrwxr-x 24 enzo enzo 2000 12 mag 23:27 WebService/
      > >
      > > Due to a typing error i have made this link.
      > > I can use this link with all other application but not with Me.
      > >
      >
      > So if you fix the link does this fix the problem? (not that this
      is an
      > excuse).
      >
      > > Ciao.
      > >
      > > Vincenzo
      > >
      >
      > Cool link.
      >
      > Does not crash on Solaris with this type of link.
      > I will have to build on Linux and debug it.
      >
      > What you should of got is this:
      >
      > Directory listing of: /home/jon/crash/
      > 10240 used in 0 files and 4 dirs (Not-Filtered)
      >
      > Attr Size Modified Name <Order by Extension>
      > drwx 8704 2007/05/28 22:20:13 ../
      > drwx 512 2007/05/28 22:20:29 WebService/
      > drwx 512 2007/05/28 22:20:29 webservice/ -> WebService//
      >
      > Following the link in the browser descends to the next directory.
      I
      > think I have reproduced it correctly as you stated above:
      >
      > cd /home/jon/crash/
      > ls -la
      >
      > total 24
      > drwxr-xr-x 3 jon users 512 May 28 22:20 .
      > drwxr-x--- 108 jon users 8704 May 28 22:20 ..
      > lrwxrwxrwx 1 jon users 12 May 28 22:20
      webservice ->
      > WebService//
      > drwxr-xr-x 2 jon users 512 May 28 22:20 WebService
      > [EXIT 0]
      >
      > Thanks for the info.
      > Regards
      > Jon.
      >
    • ZarathustraXYZ
      Your patch partially fix. Now Me don t crash but in the dir tree show the root-dir folded. Ciao. Vincenzo ... if it ... as I ... delete */ ... delete */ ...
      Message 2 of 11 , May 28, 2007
      • 0 Attachment
        Your patch partially fix. Now Me don't crash but in the dir tree
        show the root-dir folded.

        Ciao.

        Vincenzo

        --- In jasspa@yahoogroups.com, Steven Phillips <bill@...> wrote:
        >
        > I think I found and fixed this issue. Now that you have built ME
        > yourself, could you please try the following fix and let me know
        if it
        > solves the problem. Note the line numbers may not be exactly right
        as I
        > had make other commits before this one. Thanks,
        >
        > Steve
        >
        > Index: dirlist.c
        >
        ===================================================================
        > RCS file: /usr/cvs/repme/me/src/dirlist.c,v
        > retrieving revision 2.12
        > retrieving revision 2.13
        > diff -c -w -r2.12 -r2.13
        > *** dirlist.c 22 Oct 2006 16:43:14 -0000 2.12
        > --- dirlist.c 26 Oct 2006 20:01:23 -0000 2.13
        > ***************
        > *** 166,172 ****
        > /* Recursively iterate over the children and delete */
        > for (dnode = root->child; dnode != NULL; /* NULL */)
        > {
        > ! if(dnode->child != NULL)
        > dirDeleteTree (dnode);
        > dt = dnode; /* Remember node to
        delete */
        > dnode = dnode->next ; /* Point to next node */
        > --- 166,172 ----
        > /* Recursively iterate over the children and delete */
        > for (dnode = root->child; dnode != NULL; /* NULL */)
        > {
        > ! if((dnode->child != NULL) && (dnode->lname == NULL))
        > dirDeleteTree (dnode);
        > dt = dnode; /* Remember node to
        delete */
        > dnode = dnode->next ; /* Point to next node */
        > ***************
        >
        > ZarathustraXYZ wrote:
        > >
        > > Ok, I have found where is the problem.
        > > I didn't realize it before but the link that crash Me
        > > is "strange" :-), this is the output of ls -l:
        > >
        > > lrwxrwxrwx 1 enzo enzo 11 27 mag 00:35 webservice ->
        > > WebService//
        > > drwxrwxr-x 24 enzo enzo 2000 12 mag 23:27 WebService/
        > >
        > > Due to a typing error i have made this link.
        > > I can use this link with all other application but not with Me.
        > >
        > > Ciao.
        > >
        > > Vincenzo
        > >
        > > --- In jasspa@yahoogroups.com <mailto:jasspa%40yahoogroups.com>,
        > > "ZarathustraXYZ" <zarathustraxyz@>
        > > wrote:
        > > >
        > > > Hi,
        > > > file-browser recognize the symbolic links. On amd64 when I
        click
        > > (on
        > > > when I hit Return) crash without display nothing at the bottom
        (on
        > > > fedora 6 and centos 4.5 on amd64), maybe it's to fast I guess.
        On
        > > > ScientificLinux 4.5 (32 bit) it say at the
        > > > bottom "[Evaluating ... " .
        > > > I have rebuilded Me from source (my gcc is gcc version 4.1.1
        > > > 20070105 (Red Hat 4.1.1-51) and glibc is
        glibc-2.5-10.fc6.x86_64)
        > > > but this is the result :-( :
        > > >
        > > > *** glibc detected *** ./me: double free or corruption
        (!prev):
        > > > 0x00000000006d1700 ***
        > > > ======= Backtrace: =========
        > > > /lib64/libc.so.6[0x396086ea30]
        > > > /lib64/libc.so.6(cfree+0x8c)[0x396087214c]
        > > > ./me[0x40baac]
        > > > ./me[0x40c6ef]
        > > > ./me[0x40cb03]
        > > > ./me[0x41a91d]
        > > > ./me[0x41b791]
        > > > ./me[0x41bd4b]
        > > > ./me[0x41a8b6]
        > > > ./me[0x41b791]
        > > > ./me[0x41bd4b]
        > > > ./me[0x41a8b6]
        > > > ./me[0x41b791]
        > > > ./me[0x41cb0c]
        > > > ./me[0x41a91d]
        > > > ./me[0x41b791]
        > > > ./me[0x41bd4b]
        > > > ./me[0x41a8b6]
        > > > ./me[0x43a8f4]
        > > > ./me[0x43ae41]
        > > > ./me[0x43aee0]
        > > > /lib64/libc.so.6(__libc_start_main+0xf4)[0x396081da44]
        > > > ./me[0x403a09]
        > > > ======= Memory map: ========
        > > > 00400000-00487000 r-xp 00000000 08:04
        > > >
        > > 328162 /home/enzo/Programmi/microemacs/me060909/src/me
        > > > 00686000-0068f000 rw-p 00086000 08:04
        > > >
        > > 328162 /home/enzo/Programmi/microemacs/me060909/src/me
        > > > 0068f000-00738000 rw-p 0068f000 00:00 0
        > > > [heap]
        > > > 3688000000-3688104000 r-xp 00000000 08:03
        > > > 3106358 /usr/lib64/libX11.so.6.2.0
        > > > 3688104000-3688304000 ---p 00104000 08:03
        > > > 3106358 /usr/lib64/libX11.so.6.2.0
        > > > 3688304000-368830b000 rw-p 00104000 08:03
        > > > 3106358 /usr/lib64/libX11.so.6.2.0
        > > > 3688800000-3688809000 r-xp 00000000 08:03
        > > > 3127047 /usr/lib64/libXrender.so.1.3.0
        > > > 3688809000-3688a08000 ---p 00009000 08:03
        > > > 3127047 /usr/lib64/libXrender.so.1.3.0
        > > > 3688a08000-3688a09000 rw-p 00008000 08:03
        > > > 3127047 /usr/lib64/libXrender.so.1.3.0
        > > > 3689000000-368900a000 r-xp 00000000 08:03
        > > > 3127050 /usr/lib64/libXcursor.so.1.0.2
        > > > 368900a000-3689209000 ---p 0000a000 08:03
        > > > 3127050 /usr/lib64/libXcursor.so.1.0.2
        > > > 3689209000-368920a000 rw-p 00009000 08:03
        > > > 3127050 /usr/lib64/libXcursor.so.1.0.2
        > > > 3689400000-3689410000 r-xp 00000000 08:03
        > > > 3114633 /usr/lib64/libXpm.so.4.11.0
        > > > 3689410000-3689610000 ---p 00010000 08:03
        > > > 3114633 /usr/lib64/libXpm.so.4.11.0
        > > > 3689610000-3689611000 rw-p 00010000 08:03
        > > > 3114633 /usr/lib64/libXpm.so.4.11.0
        > > > 3689800000-3689805000 r-xp 00000000 08:03
        > > > 3127049 /usr/lib64/libXfixes.so.3.1.0
        > > > 3689805000-3689a04000 ---p 00005000 08:03
        > > > 3127049 /usr/lib64/libXfixes.so.3.1.0
        > > > 3689a04000-3689a05000 rw-p 00004000 08:03
        > > > 3127049 /usr/lib64/libXfixes.so.3.1.0
        > > > 3960400000-396041a000 r-xp 00000000 08:03
        > > > 1109786 /lib64/ld-2.5.so
        > > > 3960619000-396061a000 r--p 00019000 08:03
        > > > 1109786 /lib64/ld-2.5.so
        > > > 396061a000-396061b000 rw-p 0001a000 08:03
        > > > 1109786 /lib64/ld-2.5.so
        > > > 3960800000-3960944000 r-xp 00000000 08:03
        > > > 1109788 /lib64/libc-2.5.so
        > > > 3960944000-3960b44000 ---p 00144000 08:03
        > > > 1109788 /lib64/libc-2.5.so
        > > > 3960b44000-3960b48000 r--p 00144000 08:03
        > > > 1109788 /lib64/libc-2.5.so
        > > > 3960b48000-3960b49000 rw-p 00148000 08:03
        > > > 1109788 /lib64/libc-2.5.so
        > > > 3960b49000-3960b4e000 rw-p 3960b49000 00:00 0
        > > > 3961000000-3961003000 r-xp 00000000 08:03
        > > > 1109804 /lib64/libdl-2.5.so
        > > > 3961003000-3961202000 ---p 00003000 08:03
        > > > 1109804 /lib64/libdl-2.5.so
        > > > 3961202000-3961203000 r--p 00002000 08:03
        > > > 1109804 /lib64/libdl-2.5.so
        > > > 3961203000-3961204000 rw-p 00003000 08:03
        > > > 1109804 /lib64/libdl-2.5.so
        > > > 3961c00000-3961c0d000 r-xp 00000000 08:03
        > > > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
        > > > 3961c0d000-3961e0c000 ---p 0000d000 08:03
        > > > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
        > > > 3961e0c000-3961e0d000 rw-p 0000c000 08:03
        > > > 1110040 /lib64/libgcc_s-4.1.1-20070105.so.1
        > > > 3962400000-3962402000 r-xp 00000000 08:03
        > > > 3125619 /usr/lib64/libXau.so.6.0.0
        > > > 3962402000-3962601000 ---p 00002000 08:03
        > > > 3125619 /usr/lib64/libXau.so.6.0.0
        > > > 3962601000-3962602Aborted
        > > >
        > > > Ciao.
        > > >
        > > > Vincenzo
        > > >
        > > >
        > > >
        > > > --- In jasspa@yahoogroups.com
        <mailto:jasspa%40yahoogroups.com>, Jon
        > > Green <jon@> wrote:
        > > > >
        > > > > Thomas Hundt wrote:
        > > > > > FYI It's working for me (SuSE 32-bit) and it's been very
        > > stable
        > > > over the
        > > > > > past few years. What versions are you using?
        > > > > >
        > > > > > One thing I'd ask is, when you hit F10 to bring up the
        file
        > > > browser,
        > > > > > does it recognize the symbolic links? (It should display
        for
        > > > example
        > > > > > "HackSym/ -> Hack" for a link created using 'ln -s Hack
        > > > HackSym'.)
        > > > > >
        > > > > > How far does it get when it crashes? When you click on (or
        > > hit
        > > > Return
        > > > > > on) one of these entries, it says at the
        bottom, "[Evaluating
        > > > <item>]".
        > > > > > It also changes the directory tree display on the left to
        > > show
        > > > the
        > > > > > directories in the selected dir. And it changes the pane
        on
        > > the
        > > > right
        > > > > > to show the directories and files.
        > > > > >
        > > > > > -Th
        > > > > >
        > > > >
        > > > > Good point, I wonder if there is an incompatibility with the
        > > > linked
        > > > > glibc.so? Maybe need to build from source to correct the
        > > problem.
        > > > The
        > > > > current version is distributed with Gentoo and there do not
        seem
        > > > to be
        > > > > any problems with Linux.
        > > > >
        > > > > Strongly suggest a source re-build and see how it goes on
        your
        > > > system.
        > > > >
        > > > > I was going to try building this on CentOs 5.0 to see what
        > > > happens -
        > > > > will do this later in the week.
        > > > >
        > > > > Jon.
        > > > >
        > > >
        > >
        > >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.