Stuart,
Thanks, that resolves it and at least its recorded. FWIW (probably not
much):
1. Not having gdb in the base would have triggered me to pkg_add it and the
assumption was the base
gdb would be fine with the base cc.
2. But our AI masters at google suggested it was a OpenBSD policy thing
which was confusing.
3. I did of course try a vanilla install but alas no luck.
On the policy having an embedded system without a workable gdb seems to me
to be a bad idea.
Maybe given OpenBSD security it would be worth just verifying a remote
server for gdb if
people thinks it worthwhile.
Anyways dinner in Darwin, NT at your convenience.
On Wed, Aug 13, 2025 at 5:32 PM Stuart Henderson <stu.li...@spacehopper.org>
wrote:
> On 2025-08-12, Phil Maker <philip.ma...@gmail.com> wrote:
> > --000000000000975dfb063c32bcc4
> > Content-Type: text/plain; charset="UTF-8"
> >
> > G'day,
> >
> > There appears to be a dwarf versioning error between OpenBSD 7.7 and the
> > installed gdb perhaps.
> >
> > Running stock gdb and helloworld with -g ends up with the message:
> >
> > Error while reading shared library symbols:
> > Dwarf Error: wrong version in compilation unit header (is 4, should
> be
> > 2) [in module /usr/libexec/ld.so]
>
> Base does not use GPLv3 software so this is stuck at an older version.
> Please either use lldb, or pkg_add gdb and use the egdb binary from
> packages (now at 16.3 in snapshots - the 7.7 release was older but
> still usable)).
>
> Perhaps we should stop building and installing gdb on archs using the
> LLVM toolchain; it was useful once upon a time, but not so much now.
>
>
> --
> Please keep replies on the mailing list.
>
>
--
Phil Maker .
web: https://eds.power.on.net/EDS or https://eds.power.net/laot-pub
emails: <philip.ma...@gmail.com>, <p...@circularsolutions.com.au>,
<p...@circularsolutions.com.au>
<p...@gnu.org>
phone: +61 (0) 439 223 469
