On 11/24/07, Szabolcs Szakacsits <[EMAIL PROTECTED]> wrote:
> Alon, could you please make a simple segfaulting symver test case? Just a
> main() and the needed two functions, similar to the construct FUSE uses.
> No problem if not then I'll setup the needed environment, it will just
> take a bit more time.

Well... As it seems you need to be an expert in ELF more than uclibc.
I've invested some time in order to reproduce this... But as I have
not used .symver ever, I could not reproduce this.
I guess fuse developers will have better chance to understand what is
wrong, by simply compile busybox+fuse+ntfs-3g with uclibc and chroot
to this environment.

The major problem is not the segfault, but the following message:
fuse: unknown option `'

You can search and see many users reported this. Almost all results
from this root cause.

I tried the following, with no luck.

a.c:
---
#include <stdio.h>
#include "a.h"

void f1 (void) {
        printf ("f1\n");
}

void f1_compat (void) {
        printf ("f1_compat\n");
}

__asm__(".symver f1_compat,[EMAIL PROTECTED]");
---

a.h
---
void f1 (void);
---

a.version
---
A_1.0 {
};

A_1.1 {
        global:
                f1;
                f1_compat;

        local:
                *;
} A_1.0;
---

b.c
---
#include "a.h"

int main (void) {
        f1 ();
        return 0;
}
---

Makefile
---
CC := gcc
PREFIX :=

all:    b

clean:
        -rm *.o *.so.* b

b:      a.so.1 b.c
        $(PREFIX)$(CC) -fPIC -o b b.c a.so.1

a.so.1: a.c a.h a.version
        $(PREFIX)$(CC) -fPIC -o a.so.1 -shared a.c -Wl,-soname=a.so.1
-Wl,-version-number=1:1:0 -Wl,-version-script=a.version
---

Best Regards,
Alon Bar-Lev.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel

Reply via email to