#segfault — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #segfault, aggregated by home.social.
-
RipGrep musl binaries occasionally segfault during very-large searches
https://github.com/BurntSushi/ripgrep/issues/3494
Comments: https://news.ycombinator.com/item?id=49133889
#HackerNews #RipGrep #segfault #musl #binaries #search #issues #segfaults #performance
-
RipGrep musl binaries occasionally segfault during very-large searches
https://github.com/BurntSushi/ripgrep/issues/3494
Comments: https://news.ycombinator.com/item?id=49133889
#HackerNews #RipGrep #segfault #musl #binaries #search #issues #segfaults #performance
-
RipGrep musl binaries occasionally segfault during very-large searches
https://github.com/BurntSushi/ripgrep/issues/3494
Comments: https://news.ycombinator.com/item?id=49133889
#HackerNews #RipGrep #segfault #musl #binaries #search #issues #segfaults #performance
-
RipGrep musl binaries occasionally segfault during very-large searches
https://github.com/BurntSushi/ripgrep/issues/3494
Comments: https://news.ycombinator.com/item?id=49133889
#HackerNews #RipGrep #segfault #musl #binaries #search #issues #segfaults #performance
-
RipGrep musl binaries occasionally segfault during very-large searches
https://github.com/BurntSushi/ripgrep/issues/3494
Comments: https://news.ycombinator.com/item?id=49133889
#HackerNews #RipGrep #segfault #musl #binaries #search #issues #segfaults #performance
-
I'm double-checking I have everything ready for my #GPGPU lessons (course starts in March) and of course a recent upgrade seems to have busted #rusticl on my machine, with a #segfault somewhere in kernel compilation stage. Not happy about it, but I guess it's par of the course when running somewhat bleeding edge OSes (Debian unstable + some weird stuff). Let's see if this issue is fixed wth the version of Mesa in experimental, or if I can report the bug.
-
I'm double-checking I have everything ready for my #GPGPU lessons (course starts in March) and of course a recent upgrade seems to have busted #rusticl on my machine, with a #segfault somewhere in kernel compilation stage. Not happy about it, but I guess it's par of the course when running somewhat bleeding edge OSes (Debian unstable + some weird stuff). Let's see if this issue is fixed wth the version of Mesa in experimental, or if I can report the bug.
-
I'm double-checking I have everything ready for my #GPGPU lessons (course starts in March) and of course a recent upgrade seems to have busted #rusticl on my machine, with a #segfault somewhere in kernel compilation stage. Not happy about it, but I guess it's par of the course when running somewhat bleeding edge OSes (Debian unstable + some weird stuff). Let's see if this issue is fixed wth the version of Mesa in experimental, or if I can report the bug.
-
I'm double-checking I have everything ready for my #GPGPU lessons (course starts in March) and of course a recent upgrade seems to have busted #rusticl on my machine, with a #segfault somewhere in kernel compilation stage. Not happy about it, but I guess it's par of the course when running somewhat bleeding edge OSes (Debian unstable + some weird stuff). Let's see if this issue is fixed wth the version of Mesa in experimental, or if I can report the bug.
-
I'm double-checking I have everything ready for my #GPGPU lessons (course starts in March) and of course a recent upgrade seems to have busted #rusticl on my machine, with a #segfault somewhere in kernel compilation stage. Not happy about it, but I guess it's par of the course when running somewhat bleeding edge OSes (Debian unstable + some weird stuff). Let's see if this issue is fixed wth the version of Mesa in experimental, or if I can report the bug.
-
Một yêu cầu HTTP lỗi duy nhất đã làm sập toàn bộ hệ thống máy chủ sản xuất chỉ trong 90 giây. Lỗi phân đoạn (segfault) trên một máy chủ khiến bộ cân bằng tải liên tục đẩy yêu cầu lỗi này sang các máy chủ khác, gây ra sự cố dây chuyền nghiêm trọng.
#ServerDown #Segfault #LoadBalancer #TechFail #SystemFailure
#SậpMáyChủ #LỗiHệThống #BảoMậtMạng #CôngNghệ #SựCốhttps://systemdr.substack.com/p/the-poison-pill-request-how-one-bad
-
-
-
-
-
-
#GoogleChrome has stopped working on my #Debian13 #KDE system. If I do nothing it starts up the file associate GUI, if I stop it from doing that I get various errors and either it fails to start or it gives me a #segfault
It's not as if I use it much under #Linux, but it's annoying as it used to work.
I've already reinstalled it case it was a broken install - will try moving my profile out of the way and see what happens next.
-
#GoogleChrome has stopped working on my #Debian13 #KDE system. If I do nothing it starts up the file associate GUI, if I stop it from doing that I get various errors and either it fails to start or it gives me a #segfault
It's not as if I use it much under #Linux, but it's annoying as it used to work.
I've already reinstalled it case it was a broken install - will try moving my profile out of the way and see what happens next.
-
#GoogleChrome has stopped working on my #Debian13 #KDE system. If I do nothing it starts up the file associate GUI, if I stop it from doing that I get various errors and either it fails to start or it gives me a #segfault
It's not as if I use it much under #Linux, but it's annoying as it used to work.
I've already reinstalled it case it was a broken install - will try moving my profile out of the way and see what happens next.
-
#GoogleChrome has stopped working on my #Debian13 #KDE system. If I do nothing it starts up the file associate GUI, if I stop it from doing that I get various errors and either it fails to start or it gives me a #segfault
It's not as if I use it much under #Linux, but it's annoying as it used to work.
I've already reinstalled it case it was a broken install - will try moving my profile out of the way and see what happens next.
-
Ваши генераторные выражения сломаны: чиним и разбираемся
Всем привет! Меня зовут Ефимов Михаил, я профессиональный разработчик с 2010 года и начинающий contributor в CPython. Итак, название статьи говорит, что генераторные выражения сломаны. О чем вообще речь? Посмотрим на такой код, не содержащий никаких import: g = (x for x in range(10)) g.gi_frame.f_locals['.0'] = range(20) list(g) Устанавливаем с официального сайта новенький Python 3.13.0 . Запускаем интерпретатор в режиме консоли, копируем в консоль эти строки кода, ожидаем увидеть содержимое списка... А содержимого никакого нет, да и консоль закрылась - интерпретатор завершил работу. В зависимости от того, на какой операционной системе был запущен код, будет сформирован Segmentation Fault или его вариации. Например, Windows использует обозначение STATUS_ACCESS_VIOLATION , но суть та же. Что ж, всё честно, crash на месте, а теперь давайте разбираться, что вообще произошло. Благо, строчек у нас всего три, так что мы можем подробно описать все объекты, вызовы методов и функций.
https://habr.com/ru/articles/853864/
#segfault #generator_expressions #generators #comprehension #bytecode #virtual_machine
-
Ваши генераторные выражения сломаны: чиним и разбираемся
Всем привет! Меня зовут Ефимов Михаил, я профессиональный разработчик с 2010 года и начинающий contributor в CPython. Итак, название статьи говорит, что генераторные выражения сломаны. О чем вообще речь? Посмотрим на такой код, не содержащий никаких import: g = (x for x in range(10)) g.gi_frame.f_locals['.0'] = range(20) list(g) Устанавливаем с официального сайта новенький Python 3.13.0 . Запускаем интерпретатор в режиме консоли, копируем в консоль эти строки кода, ожидаем увидеть содержимое списка... А содержимого никакого нет, да и консоль закрылась - интерпретатор завершил работу. В зависимости от того, на какой операционной системе был запущен код, будет сформирован Segmentation Fault или его вариации. Например, Windows использует обозначение STATUS_ACCESS_VIOLATION , но суть та же. Что ж, всё честно, crash на месте, а теперь давайте разбираться, что вообще произошло. Благо, строчек у нас всего три, так что мы можем подробно описать все объекты, вызовы методов и функций.
https://habr.com/ru/articles/853864/
#segfault #generator_expressions #generators #comprehension #bytecode #virtual_machine
-
Ваши генераторные выражения сломаны: чиним и разбираемся
Всем привет! Меня зовут Ефимов Михаил, я профессиональный разработчик с 2010 года и начинающий contributor в CPython. Итак, название статьи говорит, что генераторные выражения сломаны. О чем вообще речь? Посмотрим на такой код, не содержащий никаких import: g = (x for x in range(10)) g.gi_frame.f_locals['.0'] = range(20) list(g) Устанавливаем с официального сайта новенький Python 3.13.0 . Запускаем интерпретатор в режиме консоли, копируем в консоль эти строки кода, ожидаем увидеть содержимое списка... А содержимого никакого нет, да и консоль закрылась - интерпретатор завершил работу. В зависимости от того, на какой операционной системе был запущен код, будет сформирован Segmentation Fault или его вариации. Например, Windows использует обозначение STATUS_ACCESS_VIOLATION , но суть та же. Что ж, всё честно, crash на месте, а теперь давайте разбираться, что вообще произошло. Благо, строчек у нас всего три, так что мы можем подробно описать все объекты, вызовы методов и функций.
https://habr.com/ru/articles/853864/
#segfault #generator_expressions #generators #comprehension #bytecode #virtual_machine
-
My favorite writing tool is KDE’s Ghostwriter markdown editor. Back in 2021, I installed Ghostwriter on a computer running Manjaro Linux and encountered a segmentation fault when I tried to launch it. I eventually found a fix and described it in an article. Since then, I had no trouble installing and running Ghostwriter on multiple systems (usually Arch-based EndeavourOS) until I installed it on my new laptop running Fedora 40. After installing, Ghostwriter failed to launch. I had a bad feeling about the culprit and confirmed when I tried to launch from the terminal that Ghostwriter had segfaulted. You may be wondering where my solution article is. For my laptop, I uninstalled the Fedora package version of Ghostwriter and replaced it with the Flatpak, which works without any problem. One reason I did not do that in 2021 was because the Flatpak (note 2021 was before Ghostwriter became a KDE app) was out of date. However, the Flatpak is now keeping up with the non-Flatpak version, so I saw no reason to not just go with it and check again later to see if the issue with the regular version resolves itself in a future release.
https://social.emucafe.org/naferrell/ghostwriter-segfault-on-fedora/
#fedora #flatpak #ghostwriterMarkdownEditor #kde #segfault #troubleshooting
-
Anyone seen this before? #FreeBSD #pkg #segfault #unbound
[1/26] Upgrading unbound from 1.19.1 to 1.19.3...
===> Creating groups.
Using existing group 'unbound'.
===> Creating users
Using existing user 'unbound'.
[1/26] Extracting unbound-1.19.3: 100%
Child process pid=30542 terminated abnormally: Segmentation faultThis is after upgrading to pkg 1.21.0, which was built at the same time. Stack trace in a followup post.
-
Anyone seen this before? #FreeBSD #pkg #segfault #unbound
[1/26] Upgrading unbound from 1.19.1 to 1.19.3...
===> Creating groups.
Using existing group 'unbound'.
===> Creating users
Using existing user 'unbound'.
[1/26] Extracting unbound-1.19.3: 100%
Child process pid=30542 terminated abnormally: Segmentation faultThis is after upgrading to pkg 1.21.0, which was built at the same time. Stack trace in a followup post.
-
Anyone seen this before? #FreeBSD #pkg #segfault #unbound
[1/26] Upgrading unbound from 1.19.1 to 1.19.3...
===> Creating groups.
Using existing group 'unbound'.
===> Creating users
Using existing user 'unbound'.
[1/26] Extracting unbound-1.19.3: 100%
Child process pid=30542 terminated abnormally: Segmentation faultThis is after upgrading to pkg 1.21.0, which was built at the same time. Stack trace in a followup post.
-
Anyone seen this before? #FreeBSD #pkg #segfault #unbound
[1/26] Upgrading unbound from 1.19.1 to 1.19.3...
===> Creating groups.
Using existing group 'unbound'.
===> Creating users
Using existing user 'unbound'.
[1/26] Extracting unbound-1.19.3: 100%
Child process pid=30542 terminated abnormally: Segmentation faultThis is after upgrading to pkg 1.21.0, which was built at the same time. Stack trace in a followup post.
-
Anyone seen this before? #FreeBSD #pkg #segfault #unbound
[1/26] Upgrading unbound from 1.19.1 to 1.19.3...
===> Creating groups.
Using existing group 'unbound'.
===> Creating users
Using existing user 'unbound'.
[1/26] Extracting unbound-1.19.3: 100%
Child process pid=30542 terminated abnormally: Segmentation faultThis is after upgrading to pkg 1.21.0, which was built at the same time. Stack trace in a followup post.
-
#Java crash bug on #macOS 14.4 is in my wheelhouse (resilience.)
Root cause seems to be they changed what signal the OS sends to a process when certain kind of mem access is attempted
In the case in question the kernel previously delivered a SIGBUS or #SIGSEGV
If you've ever heard of a program crashing via a so-called #segfault it means the process received a #SEGV sig, it did NOT handle it explicitly (& robustly) & the default behavior was to crash
now they SIGKILL it! *cannot* be handled!
-
#Java crash bug on #macOS 14.4 is in my wheelhouse (resilience.)
Root cause seems to be they changed what signal the OS sends to a process when certain kind of mem access is attempted
In the case in question the kernel previously delivered a SIGBUS or #SIGSEGV
If you've ever heard of a program crashing via a so-called #segfault it means the process received a #SEGV sig, it did NOT handle it explicitly (& robustly) & the default behavior was to crash
now they SIGKILL it! *cannot* be handled!
-
#Java crash bug on #macOS 14.4 is in my wheelhouse (resilience.)
Root cause seems to be they changed what signal the OS sends to a process when certain kind of mem access is attempted
In the case in question the kernel previously delivered a SIGBUS or #SIGSEGV
If you've ever heard of a program crashing via a so-called #segfault it means the process received a #SEGV sig, it did NOT handle it explicitly (& robustly) & the default behavior was to crash
now they SIGKILL it! *cannot* be handled!
-
#Java crash bug on #macOS 14.4 is in my wheelhouse (resilience.)
Root cause seems to be they changed what signal the OS sends to a process when certain kind of mem access is attempted
In the case in question the kernel previously delivered a SIGBUS or #SIGSEGV
If you've ever heard of a program crashing via a so-called #segfault it means the process received a #SEGV sig, it did NOT handle it explicitly (& robustly) & the default behavior was to crash
now they SIGKILL it! *cannot* be handled!
-
New blog post: 7 Beautiful SegFaults in C
https://blog.sigma-star.io/2024/01/seven-segfault/
#blog #programming #C #segfault #stack #heap -
New blog post: 7 Beautiful SegFaults in C
https://blog.sigma-star.io/2024/01/seven-segfault/
#blog #programming #C #segfault #stack #heap -
New blog post: 7 Beautiful SegFaults in C
https://blog.sigma-star.io/2024/01/seven-segfault/
#blog #programming #C #segfault #stack #heap -
New blog post: 7 Beautiful SegFaults in C
https://blog.sigma-star.io/2024/01/seven-segfault/
#blog #programming #C #segfault #stack #heap -
New blog post: 7 Beautiful SegFaults in C
https://blog.sigma-star.io/2024/01/seven-segfault/
#blog #programming #C #segfault #stack #heap -
# pkg upgrade
Updating local repository catalogue...
Child process pid=2580 terminated abnormally: Illegal instructionJe sens qu’on va passer une bonne soirée…
(MÀJ : j’ai pu m’en sortir avec pkg-static upgrade, mais d’autres commandes comme iocage continuaient de crasher. Un reboot a suffi. La machine en question est presque en âge de boire, de voter et de regarder des vidéos d’anatomie…)
-
# pkg upgrade
Updating local repository catalogue...
Child process pid=2580 terminated abnormally: Illegal instructionJe sens qu’on va passer une bonne soirée…
(MÀJ : j’ai pu m’en sortir avec pkg-static upgrade, mais d’autres commandes comme iocage continuaient de crasher. Un reboot a suffi. La machine en question est presque en âge de boire, de voter et de regarder des vidéos d’anatomie…)
-
Hard-learned tip:
when making an EditorPlugin, and you get to the exit_tree:func _exit_tree() -> void:
..remove_control_from_container(CONTAINER_SPATIAL_EDITOR_MENU, someref)
..# Without doing this, godot segfaults.
..someref.queue_free()HTH
🦇
(I know the docs warned me, but I missed it!) -
Hard-learned tip:
when making an EditorPlugin, and you get to the exit_tree:func _exit_tree() -> void:
..remove_control_from_container(CONTAINER_SPATIAL_EDITOR_MENU, someref)
..# Without doing this, godot segfaults.
..someref.queue_free()HTH
🦇
(I know the docs warned me, but I missed it!) -
Hard-learned tip:
when making an EditorPlugin, and you get to the exit_tree:func _exit_tree() -> void:
..remove_control_from_container(CONTAINER_SPATIAL_EDITOR_MENU, someref)
..# Without doing this, godot segfaults.
..someref.queue_free()HTH
🦇
(I know the docs warned me, but I missed it!) -
Hard-learned tip:
when making an EditorPlugin, and you get to the exit_tree:func _exit_tree() -> void:
..remove_control_from_container(CONTAINER_SPATIAL_EDITOR_MENU, someref)
..# Without doing this, godot segfaults.
..someref.queue_free()HTH
🦇
(I know the docs warned me, but I missed it!) -
Hard-learned tip:
when making an EditorPlugin, and you get to the exit_tree:func _exit_tree() -> void:
..remove_control_from_container(CONTAINER_SPATIAL_EDITOR_MENU, someref)
..# Without doing this, godot segfaults.
..someref.queue_free()HTH
🦇
(I know the docs warned me, but I missed it!)
