Re: Lack of TARGET_ARCH=powerpc support in kgdb from devel/gdb (e.g., -r440115 of /usr/ports): "ABI doesn't support a vmcore target"

[Mark Millard]

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 info /usr/ports | grep "Re[plv]"
> Relative URL: ^/head
> Repository Root: https://svn.freebsd.org/ports
> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
> Revision: 440115
> Last Changed Rev: 440115
> 
> (built via gcc 4.2.1: not via clang: I
> experiment with clang for powerpc and
> powerpc64 so I'm being explicit)
> 
> I end up getting the following sort of result:
> 
> # kgdb /usr/lib/debug/boot/kernel/kernel.debug /var/crash/vmcore.4 
> . . .
> Reading symbols from /usr/lib/debug/boot/kernel/kernel.debug...done.
> ABI doesn't support a vmcore target
> 
> That message is from: /usr/ports/devel/gdb/files/kgdb/fbsd-kvm.c . . .
> 
> static void
> kgdb_trgt_open(const char *arg, int from_tty)
> {
>struct fbsd_vmcore_ops *ops = (struct fbsd_vmcore_ops *)
>gdbarch_data (target_gdbarch(), fbsd_vmcore_data);
> . . .
>if (ops == NULL || ops->supply_pcb == NULL || ops->cpu_pcb_addr == 
> NULL)
>error ("ABI doesn't support a vmcore target");
> . . .
> 
> It appears that there is no kernel debugging
> supported for TARGET_ARCH=powerpc currently.
> (The system no longer has its own gdb related
> materials.)

I've discovered more context and have found
a few of issues in how things are currently
set up.

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 binary in /usr/local/bin/gdb /usr/libexec/gdb /usr/bin/gdb; do
if [ -x ${binary} ]; then
GDB=${binary}
return
fi
done
}

But it appears that on powerpc /usr/local/bin/gdb and
/usr/local/bin/kgdb do not support TARGET_ARCH=powerpc
at all for such activity.


THING #1:

Another oddity is for the combination:

${MK_GDB} == no && ${MK_GDB_LIBEXEC} == yes

where the tools/build/mk/OptionalObsoleteFiles.inc
logic then adds the libexec gdb and kgdb to
OLD_FILES :

.if ${MK_GDB} == no || ${MK_GDB_LIBEXEC} == no
OLD_FILES+=usr/libexec/gdb
OLD_FILES+=usr/libexec/kgdb
.endif

so doing a delete-old removes the only system
gdb and kgdb that are installed for such a
context. It does this because of:

${MK_GDB} == no

(And that explains why I thought gdb and kgdb
were not in the system.)


THING #2:

/usr/libexec/kgdb (when present) does not support the
powerpc architecture for head either . . .

On a head -r317820 powerpc I attempted:

# /usr/libexec/kgdb /usr/lib/debug/boot/kernel/kernel.debug /var/crash/vmcore.7
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "powerpc-marcel-freebsd"...
Failed to open vmcore: unsupported architecture



===
Mark Millard
markmi at dsl-only.net

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Lack of TARGET_ARCH=powerpc support in kgdb from devel/gdb (e.g., -r440115 of /usr/ports): "ABI doesn't support a vmcore target"

[Mark Millard]

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://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 440115
Last Changed Rev: 440115

(built via gcc 4.2.1: not via clang: I
experiment with clang for powerpc and
powerpc64 so I'm being explicit)

I end up getting the following sort of result:

# kgdb /usr/lib/debug/boot/kernel/kernel.debug /var/crash/vmcore.4 
. . .
Reading symbols from /usr/lib/debug/boot/kernel/kernel.debug...done.
ABI doesn't support a vmcore target

That message is from: /usr/ports/devel/gdb/files/kgdb/fbsd-kvm.c . . .

static void
kgdb_trgt_open(const char *arg, int from_tty)
{
struct fbsd_vmcore_ops *ops = (struct fbsd_vmcore_ops *)
gdbarch_data (target_gdbarch(), fbsd_vmcore_data);
. . .
if (ops == NULL || ops->supply_pcb == NULL || ops->cpu_pcb_addr == NULL)
error ("ABI doesn't support a vmcore target");
. . .

It appears that there is no kernel debugging
supported for TARGET_ARCH=powerpc currently.
(The system no longer has its own gdb related
materials.)

===
Mark Millard
markmi at dsl-only.net

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg and packages

[Kevin Oberman]

On Fri, May 5, 2017 at 3:11 PM, Sebastian Schwarz 
wrote:

> On 2017-05-04, scratch65...@att.net wrote:
> > I can't imagine what code could possibly be in thunar and
> > samba that the xfce desktop would need, (...)
>
> Thunar is used to display the icons on the XFCE desktop.  It
> depends on gvfs, which is used for accessing remote file systems
> and the trash inside Thunar.  gvfs in turn depends on samba44 in
> order to access CIFS/SMB shares.
>
> Strictly speaking some of these features might be optional.  But
> as far I know pkg currently doesn't have a concept of optional
> dependencies.  So it's an all or nothing decision, when building
> the packages.
>

This is the case. If you want to stick with packages, at least until some
new packaging features are available, your best bet is to install
ports-mgmt/synth. Then you can use it to add a private repository of all
ports that you want built with non-standard options. Then have synth create
a custom Thunar package that you can then use to avoid samba (44 or 46) or,
if supported, build Thunar against the samba version of your choosing.

synth(8) has excellent documentation on how to configure and use it. I
recommend it for the type of issue you are running into. (N.B. synth is
written in ADA and, for that reason, I don't recommend building synth from
source as that requires a major installation of the ADA compiler.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
math/giacxcas   | 1.2.2-57| 1.2.3-39
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keeping VuXML DB updated

[Walter Schwarzenfeld]

Update is on the way:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216658

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Keeping VuXML DB updated

[Kurt Jaeger]

Hi!

> Due to a vulnerability issue earlier with a port, I received some kind 
> emails of using the command below to update the VuXML DB (which is not a 
> part of the ports tree).
> 
> I did so on my server and got the following output:
> 
> --- cut ---
> 
>  > pkg audit -F
> vulnxml file up-to-date
> tiff-4.0.7_1 is vulnerable:
> tiff -- multiple vulnerabilities
> CVE: CVE-2017-7602
[...]

> What is the next procedure to follow; should I inform the port 
> maintainer of the reported port

portmgr knows about this, but there's no solution right now.

> ((ports are a user group effort) ) or 
> should I update this port with "DISABLE_VULNERABILITIES=yes" ?

There are ports that depend on tiff, and maybe you are using one
of them. If you do not need those other ports, remove tiff.

Otherwise: this (DISABLE_VULNERABILITIES) is, while not perfect,
the next step.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Keeping VuXML DB updated

[Jos Chrispijn]

Due to a vulnerability issue earlier with a port, I received some kind 
emails of using the command below to update the VuXML DB (which is not a 
part of the ports tree).


I did so on my server and got the following output:

--- cut ---

> pkg audit -F
vulnxml file up-to-date
tiff-4.0.7_1 is vulnerable:
tiff -- multiple vulnerabilities
CVE: CVE-2017-7602
CVE: CVE-2017-7601
CVE: CVE-2017-7600
CVE: CVE-2017-7599
CVE: CVE-2017-7598
CVE: CVE-2017-7597
CVE: CVE-2017-7596
CVE: CVE-2017-7595
CVE: CVE-2017-7594
CVE: CVE-2017-7593
CVE: CVE-2017-7592
CVE: CVE-2017-5225
WWW: 
https://vuxml.FreeBSD.org/freebsd/2a96e498-3234-4950-a9ad-419bc84a839d.html


1 problem(s) in the installed packages found.

--- cut ---

What is the next procedure to follow; should I inform the port 
maintainer of the reported port ((ports are a user group effort) ) or 
should I update this port with "DISABLE_VULNERABILITIES=yes" ?


Happy to contribute,
Jos Chrispijn

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: ICU Portupdate faulty

[Jos Chrispijn]

Thanks y'all for your support - this was a real eye opener.

Best regards,
Jos

Op 5-5-2017 om 19:19 schreef Kevin Oberman:
On Fri, May 5, 2017 at 6:37 AM, Jos Chrispijn 
> wrote:



Op 5-5-2017 om 18:05 schreef Adam Weinberger:

On 5 May, 2017, at 9:48, mokhi > wrote:

Well, as I can see here <
http://www.freshports.org/devel/icu/
 > an
older version of this port is vulnerable not current version.
Maybe by updating your tree your problem will be solved :-]

Yes, this is the correct answer. After icu got patched, the
VuXML entry was lowered to mark 58.2_2,1 as non-vulnerable.
Jos, it sounds like your ports tree is after the icu update
but before the VuXML modification. Update your ports tree to
bring in the new VuXML file and you should be good.

Adam, perhaps I am missing the clue here:

- I had the correct updated version in my ports collection
- Updating the vulnerable installed icu version with that version
should not provide the Vulnerability message as that version is
updates with the correct version in my icu port.

In my case, Jim's suggestion to use "DISABLE_VULNERABILITIES=yes"
was the only way of getting my faulty icu version updated to the
version that is in my port.

Kind of confused,
Jos 



The VuXML DB is not a part of the ports tree. It is usually updated by 
the nightly periodic script, but you can manually fetch it with "pkg 
audit -F -q".

--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com 
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"