Release candidate 3 is out, and I'm running it: Testing
the bleeding edge, so you don't have to.(tm)
Release candidate 3 is out, and I'm running it: Testing
the bleeding edge, so you don't have to.(tm)
On Wed, 11 Mar 2026 01:12:41 +0000, vallor wrote:
Release candidate 3 is out, and I'm running it: Testing
the bleeding edge, so you don't have to.(tm)
You shouldn't have to do that.
Just your buddy AI to look at the code and report any flaws.
On 3/10/2026 9:12 PM, vallor wrote:
Release candidate 3 is out, and I'm running it: Testing
the bleeding edge, so you don't have to.(tm)
Where's your test suite?
At Tue, 10 Mar 2026 22:29:46 -0400, DFS <[email protected]> wrote:
On 3/10/2026 9:12 PM, vallor wrote:
Release candidate 3 is out, and I'm running it: Testing
the bleeding edge, so you don't have to.(tm)
Where's your test suite?
In Steam... ;)
(I hammer on it with Elite Dangerous Odyssey.)
But you know, that's a good question. I just run it on my
daily driver. I should run "crashme" (assuming it's still around).
Incidentally, updated video drivers to latest beta.
And finally: someone tell Loco Larry to speak English, please.
Release candidate 3 is out, and I'm running it: Testing the bleeding
edge, so you don't have to.(tm)
At Wed, 11 Mar 2026 03:20:18 +0000, vallor <[email protected]> wrote:
At Tue, 10 Mar 2026 22:29:46 -0400, DFS <[email protected]> wrote:
On 3/10/2026 9:12 PM, vallor wrote:
Release candidate 3 is out, and I'm running it: Testing
the bleeding edge, so you don't have to.(tm)
Where's your test suite?
In Steam... ;)
(I hammer on it with Elite Dangerous Odyssey.)
But you know, that's a good question. I just run it on my
daily driver. I should run "crashme" (assuming it's still around).
Incidentally, updated video drivers to latest beta.
And finally: someone tell Loco Larry to speak English, please.
Running it now for 1hr:
$ crashme +2000 666 100 1:00:00 1
Crashme: (c) Copyright 1990-2012 George J. Carrette
Version: 2.8.5 6-AUG-2014
From http://alum.mit.edu/www/gjc/crashme.html
With http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html
crashme +2000 666 100 1:00:00 1
Subprocess run for 3600 seconds (0 01:00:00)
CRASHPRNG 2 Mersenne twister.
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** stack smashing detected ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
*** longjmp causes uninitialized stack frame ***: terminated
[...]
*** longjmp causes uninitialized stack frame ***: terminated
*** stack smashing detected ***: terminated
On Wed, 11 Mar 2026 03:29:05 +0000, vallor wrote:
*** longjmp causes uninitialized stack frame ***: terminated
*** stack smashing detected ***: terminated
It's those idiotic security "features."
In this case we see the insertion of a random value (canary)
into the stack frame.
With my highly tuned kernel this bullshit would never happen.
The smart GNU/Linux user disables ALL security. It is useless
excess baggage that degrades performance.
Yet my Threadripper walks away from your tricycle, Geezer.
On Wed, 11 Mar 2026 15:06:42 +0000, vallor wrote:
Yet my Threadripper walks away from your tricycle, Geezer.
Hardly.
My 12-year-old Core i7-4770 nearly smoked the Apple M2 of
Melzzz on the scimark4 benchmark. In fact, he was so
flustered that he accused me of fabricating the results.
If I had been using a distro system I would have been left
in the dust.
Security. Performance. Pick any one.
At Wed, 11 Mar 2026 14:54:43 +0000, Farley Flud <[email protected]> wrote:
On Wed, 11 Mar 2026 03:29:05 +0000, vallor wrote:
*** longjmp causes uninitialized stack frame ***: terminated
*** stack smashing detected ***: terminated
It's those idiotic security "features."
In this case we see the insertion of a random value (canary)
into the stack frame.
With my highly tuned kernel this bullshit would never happen.
The smart GNU/Linux user disables ALL security. It is useless
excess baggage that degrades performance.
Yet my Threadripper walks away from your tricycle, Geezer.
You are, by far, the worst advocate for Linux to ever post
here.
You carry your bowels in your head, and the resulting
effluvia just pours forth into your newsreader.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,099 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492380:45:05 |
| Calls: | 14,106 |
| Calls today: | 2 |
| Files: | 187,124 |
| D/L today: |
2,828 files (1,161M bytes) |
| Messages: | 2,496,308 |
| Posted today: | 1 |