Date: Sun, 15 Jan 2006 05:08:29 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Jason Evans <jasone@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/stdlib malloc.c Message-ID: <20060115030829.GA89140@flame.pc> In-Reply-To: <20060115024627.GA75521@flame.pc> References: <200601121809.k0CI9QGV028693@repoman.freebsd.org> <AD9B1A12-47F1-4EA1-B270-CC83D3149543@freebsd.org> <20060112182804.GA1047@flame.pc> <20060113012900.GA16082@flame.pc> <554CC8A8-35FB-424A-B883-505C26ECBBE8@FreeBSD.org> <20060114213238.GA15253@flame.pc> <6FD0F2BA-88E3-4E82-A5F8-D89051AEEECA@FreeBSD.org> <20060115024627.GA75521@flame.pc>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-01-15 04:46, Giorgos Keramidas <keramida@ceid.upatras.gr> wrote: > It seems strange that most of the addresses are in the 0x800000000+ > range and the adress that triggers the core dump is much smaller: > > (gdb) x/s 0x30e3100 > 0x30e3100: <Address 0x30e3100 out of bounds> > > But the real string I typed when irssi crashed is available at: > > (gdb) x/s 0x8030e3100 > 0x8030e3100: "/nick" > > Hmmm... this is definitely a bug, but it looks more like a bug in irssi > now. I wonder where that address is stripped from it's highest bit! Solved. I'll submit a patch to the maintainer of the irc/irssi port.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060115030829.GA89140>