[I've submitted bugzilla 219153 for this libvm issue of
not handling powerpc's/powerp64's ET_DYN vmcore.* 's and
such.]
On 2017-May-8, at 1:18 PM, Mark Millard wrote:
> [Mostly: Why THING #2 fails: checks for ET_EXEC
> but the actual vmcore.* 's have ET_DYN instead.]
>
> On 2017-May-8, at 11:30
[Mostly: Why THING #2 fails: checks for ET_EXEC
but the actual vmcore.* 's have ET_DYN instead.]
On 2017-May-8, at 11:30 AM, John Baldwin wrote:
> On Saturday, May 06, 2017 10:03:57 PM Mark Millard wrote:
>> THING #0:
>>
>> It appears that usr.sbin/crashinfo/crashinfo.sh assumes
>> that /usr/lo
On Saturday, May 06, 2017 10:03:57 PM Mark Millard wrote:
> THING #0:
>
> It appears that usr.sbin/crashinfo/crashinfo.sh assumes
> that /usr/local/bin/gdb will work better for all architectures,
> including for kgdb types of activity:
>
> find_gdb()
> {
> local binary
>
> for bi
[This update just notes that it appears that combination
${MK_GDB} == no && ${MK_GDB_LIBEXEC} == yes is not intended
to be used, effectively eliminating "THING #1" of 0-2.]
On 2017-May-6, at 10:03 PM, Mark Millard wrote:
> On 2017-May-6, at 5:21 PM, Mark Millard wrote:
>
>> On:
>>
>> # uname
On 2017-May-6, at 5:21 PM, Mark Millard wrote:
> On:
>
> # uname -apKU
> FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc powerpc
> 1200030 1200030
>
> When I attempt to use:
>
> # which kgdb
> /usr/local/bin/kgdb
>
> that was from building devel/gdb for:
>
> # svnlite
On:
# uname -apKU
FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc powerpc
1200030 1200030
When I attempt to use:
# which kgdb
/usr/local/bin/kgdb
that was from building devel/gdb for:
# svnlite info /usr/ports | grep "Re[plv]"
Relative URL: ^/head
Repository Root: https:/
