RE: Compile Warnings.

"Valnir" <[email protected]> Wed, 22 Nov 2006 18:54:21 -0500
Newsgroups gmane.games.devel.mud.rom
Message-ID <[email protected]>
Ok.. The socklen_t fixed the warning. I get a crash when I try to login =
though. It get's through the initial account login screen and when it =
asks me for what character I want to login as it crashes when it tries =
to set the host. We keep a list of the last 5 hosts logged in from, for =
tracking purposes. That's where it's crashing is when it's trying to =
update that.

I copied the output of gdb from the core.

Failed to read a valid object file image from memory.
Core was generated by `../src/lotn 5400'.
Program terminated with signal 11, Segmentation fault.

warning: svr4_current_sos: Can't read pathname for load map: =
Input/output error

Reading symbols from /lib/libcrypt.so.1...done.
Loaded symbols for /lib/libcrypt.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
#0  0x080b36a8 in set_host (ch=3D0xb74c58b8, d=3D0xb74c375c) at =
comm.c:5793
5793                free_string(ch->usrdata->alt_hosts[h]);
(gdb) where
#0  0x080b36a8 in set_host (ch=3D0xb74c58b8, d=3D0xb74c375c) at =
comm.c:5793
#1  0x080a8fc8 in nanny (d=3D0xb74c375c, argument=3D0xb74c3b7d "Valnir") =
at comm.c:2560
#2  0x080a49b5 in game_loop_unix (control=3D4) at comm.c:885
#3  0x080a4390 in main (argc=3D2, argv=3D0xbf916b54) at comm.c:490
(gdb)

Again, thanks!

- Valnir


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Valnir
Sent: Wednesday, November 22, 2006 6:33 PM
To: 'Michael Barton'; [email protected]
Subject: RE: Compile Warnings.

I'll check the socklen_t. Thanks for the idea. Could it be a 64-bit =
kernel, even though it's got a 32-bit (AMD Athlon XP 3000+) processor?

I am copying out of SecureCRT from being SSH'd into the box. It shows =
that way in the SSH window. I think it shows that way at the console as =
well. The ~ and (tm) aren't there, but the aE is... It's more an =
annoyance than a requirement. Thanks for any input though.

- Valnir
=20

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Michael =
Barton
Sent: Wednesday, November 22, 2006 5:23 PM
To: [email protected]
Subject: Re: Compile Warnings.

The difference is probably that your new host is running a 64-bit =
kernel.

Make sure size is defined as a socklen_t.  That's the convention on =
Linux and BSD.

Unixes that don't have a TCP stack based on BSD's differ on the type of =
pointer that goes there, and unsigned int was the most portable thing to =
do before 64-bit machines came around.

As for the weird quote characters, I have no idea.  It looks like
UTF-8 flattened to ASCII (on account of the multiple bytes in the =
extended-ascii range for each character).  What apps are you copying =
them from and to?




On 11/22/06, Valnir <[email protected]> wrote:
> Hey guys. Everyone was complaining about not having any traffic on=20
> this list, so here's something to get you thinking over the long =
weekend.
>
> I am running my mud on WolfPaw and everything compiles perfect. No=20
> errors, no warnings. All good. I am thinking about moving where my mud =

> is hosted though. The new server is running Fedora Core 5 with GCC
> 4.1.1 and I get an interesting compliation warning:
>
> gcc -c -Wall -g3  comm.c
> comm.c: In function =
=C3=A2=E2=82=AC=CB=9Cinit_descriptor=C3=A2=E2=82=AC=E2=84=A2:
> comm.c:986: warning: pointer targets in passing argument 3 of=20
> =C3=A2=E2=82=AC=CB=9Cgetsockname=C3=A2=E2=82=AC=E2=84=A2 differ in =
signedness
> comm.c:987: warning: pointer targets in passing argument 3 of=20
> =C3=A2=E2=82=AC=CB=9Caccept=C3=A2=E2=82=AC=E2=84=A2 differ in =
signedness
> comm.c:1010: warning: pointer targets in passing argument 3 of=20
> =C3=A2=E2=82=AC=CB=9Cgetpeername=C3=A2=E2=82=AC=E2=84=A2 differ in =
signedness
>
> It's a clean make, so I know it's getting all the Fedora header files=20
> with nothing left over from the WolfPaw build. I went ahead and tried=20
> to run it to see what it would do, but as I expected (since the=20
> warning is in the descriptor stuff) it crashed as soon as I tried to =
log in.
>
> Also, just on a side note. Any idea how to get the =
=C3=A2=E2=82=AC=CB=9Caccept=C3=A2=E2=82=AC=E2=84=A2 to=20
> show up as `accept' instead?
>
> Thanks!
>
> - Valnir
>
> --
> ROM mailing list
> [email protected]
> Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom
>
--
ROM mailing list
[email protected]
Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom


--
ROM mailing list
[email protected]
Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom


-- 
ROM mailing list
[email protected]
Unsubscribe here ->>> http://www.rom.org/cgi-bin/mailman/listinfo/rom