On Sat, Aug 17, 2024 at 09:44:16PM +0200, Walter Alejandro Iglesias wrote:
> On Sat, Aug 17, 2024 at 06:06:39PM +0200, Matthieu Herrb wrote:
> > On Sat, Aug 17, 2024 at 05:25:31PM +0200, Walter Alejandro Iglesias wrote:
> > > If I run gdb on the Xorg.core I got:
> > >
> > > $ egdb -ex bt -batch -c
On 2024/08/18 09:09, Walter Alejandro Iglesias wrote:
> I still don't understand how gdb(1) works. Today I ran the same command
> against the same Xorg.core file but I got different messages. The whole
> egdb output:
>
> $ egdb -q $(which X) Xorg.core
> Reading symbols from /usr/X11R6/bin/X...
[
On Sun, Aug 18, 2024 at 11:58:33AM +0100, Stuart Henderson wrote:
> On 2024/08/18 09:09, Walter Alejandro Iglesias wrote:
> > I still don't understand how gdb(1) works. Today I ran the same command
> > against the same Xorg.core file but I got different messages. The whole
> > egdb output:
> >
>
And I should add, the data in the report is from after I did another
sysupgrade -s followed by pkg_add -vurm and observing that the problem
had not gone away.
I assume and hope there is some relatively obvious fix for this. I look
forward to reading my backlog of openbsd.org mail :)
All the best
It looks like the original report got eaten somewhere or at least has
not yet reached the marc.info archive, so I am putting the sendbug -P
output with my explanatory comments at
https://nxdomain.no/~peter/sendbug-p-skapet_exim_20240818.txt
All the best,
Peter
--
Peter N. M. Hansteen, member of
Original message didn't show up.
Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
('cvs up -D 2024/07/29' in mail/exim) to see whether it was the update
or something else causing it?
On 2024/08/18 14:14, Peter N. M. Hansteen wrote:
> And I should add, the data in the report i
On 2024/08/18 13:57, Stuart Henderson wrote:
> Original message didn't show up.
Ah it showed up now.
: >Fix:
: To be determined. Likely abi mismatch between exim and libressl
that's unlikely.
> Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
> ('cvs up -D 2024/07/2
On Sun, Aug 18, 2024 at 01:58:31PM +0100, Stuart Henderson wrote:
> On 2024/08/18 13:57, Stuart Henderson wrote:
> > Original message didn't show up.
>
> Ah it showed up now.
>
> : >Fix:
> : To be determined. Likely abi mismatch between exim and libressl
>
> that's unlikely.
yes.
>> 20
On Sun, Aug 18, 2024 at 03:07:15PM +0200, Theo Buehler wrote:
> >> 2024-08-18 13:20:39 1sfdxf-6KQ-0Em4 SIGSEGV (fault address:
> >> 0x5e2f61b7)
> >> 2024-08-18 13:20:39 1sfdxf-6KQ-0Em4 SIGSEGV (maybe attempt to
> >> write to immutable memory)
>
> These strings aren't in a current
On Sun, Aug 18, 2024 at 01:57:11PM +0100, Stuart Henderson wrote:
>
> Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
> ('cvs up -D 2024/07/29' in mail/exim) to see whether it was the update
> or something else causing it?
It's 4.98, all of the freshest flavors here :)
Anyw
On Sun, Aug 18, 2024 at 03:29:25PM +0200, Peter N. M. Hansteen wrote:
> If it doesn't, the next step is of course a locally built exim 4.91.1.
make that locally built 4.97.1 but I guess it was obvious.
Also, looking at the FAQ's recipe for building kernels, I assume a
common beginner mistake woul
On Sun, Aug 18, 2024 at 03:07:15PM +0200, Theo Buehler wrote:
> kernel that you built yourself? It looks like something was in snaps
> but that diff seems to have been pulled. There haven't been recent
> changes in libssl or libcrypto that would explain this change of
> behavior.
Running with a ke
On Sun, Aug 18, 2024 at 01:57:11PM +0100, Stuart Henderson wrote:
> Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
> ('cvs up -D 2024/07/29' in mail/exim) to see whether it was the update
> or something else causing it?
downgrading to exim 4.97.1 has tls mail flowing again,
Last time when I tried to compile xenocara with debug symbols I forgot
to before remove this file /usr/xobj/xorg-config.cash.amd64, as
explained in Readme.md. Let's see if this output is useful:
$ egdb $(which X) Xorg.core
Reading symbols from /usr/X11R6/bin/X...
[New process 532413]
[New process
Hey there,
I'm running OpenBSD 7.5 as a domU on top of Xen 4.18. After updating the dom0
(from NetBSD 9.3 to 10.0), xnf in the OpenBSD domU now panics on boot
consistently (I can still get into the system if I disable xnf via boot -c). I
tried reinstalling the kernel+sets in case something got
I also have a problem with X11/xenodm.
Upon a boot (or manual xenodm start) the entire screen freezes, like I cannot
even go to the 1st tty, which is quite strange indeed, I believe that this
indicates a freeze of the entire computer, because when I tell it to go to the
1st tty, it doesn't for some
On 8/18/24 4:58 PM, Peter N. M. Hansteen wrote:
On Sun, Aug 18, 2024 at 01:57:11PM +0100, Stuart Henderson wrote:
Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
('cvs up -D 2024/07/29' in mail/exim) to see whether it was the update
or something else causing it?
downgra
17 matches
Mail list logo
