https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219153
--- Comment #6 from Mark Millard <mar...@dsl-only.net> --- (In reply to John Baldwin from comment #5) I've used both gdb's as well but I've had more occasions when system's gdb worked and ports did not than the other way around (when there is a distinction). (Historically, not just now.) Okay I'll poke at ps -M and the /usr/local/bin/gdb crash. Be warned: I'm also currently evidence-gathering for two folks working on the clang powerpc and/or powerpc64 targeting support so my FreeBSD time is split. This also leads to context switching between a world built with gcc 4.2.1 and one built with clang. If I'm interrupted I can forget to switch and, for example, end up seeing the clang issues without initially noticing why (clang built system libraries, for example). I'll rerun the /usr/local/bin/gdb test explicitly on a gcc 4.2.1 built world just in case that happened yesterday. (clang generates powerpc and powerpc64 "code" that has handling of thrown-C++-exceptions completely broken, leading to segmentation faults while trying to reach landing-pad code. "Code": incomplete dwarf information.) -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
