Issue information

Issue ID
#733
Status
Fixed
Severity
None
Started
Hercules Elf Bot
Jan 1, 2008 19:55
Last Post
Hercules Elf Bot
Jan 1, 2008 19:55
Confirmation
N/A

Hercules Elf Bot - Jan 1, 2008 19:55

Originally posted by [b]Pinky[/b]
http://www.eathena.ws/board/index.php?autocom=bugtracker&showbug=733

Well i am using eA 11999 with Debian 4.0 64bits, i compiled it and i had a few skipping warnings:

QUOTE
/usr/bin/ld: skipping incompatible /usr/lib/librt.so when searching for -lrt
/usr/bin/ld: skipping incompatible /usr/lib/librt.a when searching for -lrt
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libm.a when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libz.so when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/libz.a when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/libdl.so when searching for -ldl
/usr/bin/ld: skipping incompatible /usr/lib/libdl.a when searching for -ldl
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
/usr/bin/ld: skipping incompatible /usr/lib/libc.a when searching for -lc


flaviojs said not to worry about it since it would grab the 32bits ones instead or something... so i continued.

Now, i get this crash a lot of times, i dont know if its because of the skipping issue or just the src itself.

QUOTE
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 4158920896 (LWP 27986)]
0xf7f1d5cc in send () from /lib32/libc.so.6
(gdb) Program received signal SIGPIPE, Broken pipe.
Undefined command: "Program". Try "help".
(gdb) [Switching to Thread 4158576832 (LWP 27991)]
Undefined command: "". Try "help".
(gdb) 0xf7ec95cc in send () from /lib32/libc.so.6
Undefined command: "0xf7ec95cc". Try "help".
(gdb) handle SIGPIPE nostop
Signal Stop Print Pass to program Description
SIGPIPE No Yes Yes Broken pipe
(gdb) handle SIGPIPE noprint
Signal Stop Print Pass to program Description
SIGPIPE No No Yes Broken pipe
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /home/twilight/trunk/map-server_sql
warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4
[Thread debugging using libthread_db enabled]
[New Thread 4158572736 (LWP 28106)]


There, i rebooted the server with no prints.

And after a while.... it crashes again:

QUOTE
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4158572736 (LWP 28106)]
status_get_sc (bl=0x0) at status.c:4381
4381 switch (bl->type) {
(gdb)


This post has been edited by Pinky: Jan 1 2008, 12:02 PM