Date: Sun, 19 May 2019 20:04:50 +0200 From: Andrea Venturoli <ml@netfence.it> To: Jan Beich <jbeich@FreeBSD.org> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-ports@freebsd.org Subject: Re: Samba dump (useless) core Message-ID: <6c1c31cb-8ee7-db9c-adb0-58fec67e87c3@netfence.it> In-Reply-To: <f89679c2-0610-c533-3f3a-2496993ce187@netfence.it> References: <169305b9-64ea-6305-8ef2-9c11b8c9baf3@netfence.it> <20190508102504.GY2748@kib.kiev.ua> <0eb47166-ddaf-d0ed-7730-91341634c72c@netfence.it> <k1f1-uq4m-wny@FreeBSD.org> <f89679c2-0610-c533-3f3a-2496993ce187@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/18/19 4:14 PM, Andrea Venturoli wrote: > I'm not saying it's solved, however, since these dumps in the past have > stopped appearing several times, and later started happening again; so > I'll have to keep an eye on this. Ok, so new dumps have allowed to better pinpoint where the overflow happens and write a 20 line C program to deterministically reproduce the problem. This is *NOT* in Samba code, but in FreeBSD base system! So the next question: I would like to step into libc (or other base libraries) functions with GDB. How do I do that? I have src and debug libraries installed, e.g. /usr/lib/debug/lib/libc.so.7.debug. GDB sees those files, but still won't step into them. Also, if I issue "file /usr/lib/debug/lib/libc.so.7.debug", I get "/usr/lib/debug/lib/libc.so.7.debug: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), corrupted program header size, with debug_info, not stripped". Is that "corrupted program header size" normal? bye & Thanks av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6c1c31cb-8ee7-db9c-adb0-58fec67e87c3>