bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/6511] segmentation fault building final object


From: frediano dot ziglio at vodafone dot com
Subject: [Bug ld/6511] segmentation fault building final object
Date: 21 May 2008 14:23:12 -0000

------- Additional Comments From frediano dot ziglio at vodafone dot com  
2008-05-21 14:23 -------
I tried the patch. It just move the problem but it core after some while...
I tried to produce a test case but after three hours I got two c files that make
ld core only if compiled with some parameters (like -g or not). It always happen
if I use visibility modifier in gcc 4.1.1. Perhaps is the compiler I used?

Well... after the reduction

I tried the patch. It just move the problem but it core after some while...
I tried to produce a test case but after three hours I got two c files that make
ld core only if compiled with some parameters (like -g or not). It always happen
if I use visibility modifier in gcc 4.1.1. Perhaps is the compiler I used?

$ hppa64-hp-hpux11.00-gcc -O2 -c ctutil.c && hppa64-hp-hpux11.00-gcc -fPIC -O2
-c ct.c && hppa64-hp-hpux11.00-ld -shared ct.o ctutil.o
hppa64-hp-hpux11.00-ld: ctutil.o: invalid string offset 1734672384 >= 27 for
section `.strtab'

$ cat ct.c

struct context1
{
 int (*msg_handler) (void);
};

struct context2
{
 struct context1 *tds_ctx;
};

#pragma GCC visibility push(hidden)
int _ct_handle_server_message(void);
#pragma GCC visibility pop


int
foo1(struct context2 * ctx)
{
 ctx->tds_ctx->msg_handler = _ct_handle_server_message;
 return 345;
}


$ ctutil.c

#pragma GCC visibility push(hidden)
int _ct_handle_server_message(void);
#pragma GCC visibility pop

int
_ct_handle_server_message(void)
{
 return 0;
}

$

however if I remove ct.o from ld command it handle ctutil.o... I really don't
understand. Can I send binary object files ?? They are quite small (about 1 kb)

Frediano


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=6511

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]