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

Re: ulogd unaligned trap

On Wed, Jan 25, 2006 at 12:49:04AM +0000, Carlos Rodrigues wrote:
> On 1/24/06, Jay Estabrook <Jay.Estabrook@hp.com> wrote:
> > I think you can use "ldd /wherever/you/find/ulogd" to print the
> > libraries used by "ulogd" and where they are relocated to; that should
> > at least give the library the unaligned accesses come from...

> Ok, so here it is...

> ulisses:~# ldd /usr/sbin/ulogd
>         libdl.so.2.1 => /lib/libdl.so.2.1 (0x0000020000038000)
>         libc.so.6.1 => /lib/libc.so.6.1 (0x000002000004c000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0000020000000000)

> Not much there. So, it seems that those addresses belong to something
> related to glibc.

> Any ideas how I can trace this down? One of the machines isn't on
> production, so I can try to see exactly where these messages are
> triggered. However, I don't exactly see how to do this using
> ltrace/strace... (since the messages are generated by the kernel).


It might be nice if someone would be willing to take this code and merge it
with the existing prctl package (currently ia64-only).

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply to: