Date: Tue, 17 Jan 2017 19:41:47 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216132] devel/gdb: at e.g. -r431413: get_core_register_section can get SIGSEGV from NULL regset arguments Message-ID: <bug-216132-13-suZ0IsGQkM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-216132-13@https.bugs.freebsd.org/bugzilla/> References: <bug-216132-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216132 --- Comment #2 from Mark Millard <markmi@dsl-only.net> --- I'll note that I use the likes of: # /usr/local/bin/gdb GNU gdb (GDB) 7.12 [GDB v7.12 for FreeBSD] . . . (gdb) set gnutarget arm-gnueabi-freebsd (gdb) core-file qemu_gmake.core=20 [New process 51247] Segmentation fault (core dumped) Without the gnutarget specification I just get: "/root/poudriere_failure/work/binutils-2.27/ld/qemu_gmake.core" is not a co= re dump: File format is ambiguous Does doing similarly let you progress? As for providing the core file. . . It is from a gmake crash (GPLv3). As near as I can tell uploading the arm gmake file and/or the qemu_gmake.core file is a binary distribution under GPLv3 and would introduce whatever obligations GPLv3 indicates. I'll look and see if I'm willing to do whatever GPLv3 indicates. Otherwise I'd need to come up with an example core file that does not impose such obligations. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216132-13-suZ0IsGQkM>