Nп/п : 23 из 100
От : Richard Kettlewell 2:5075/128 15 сен 23 11:58:09
К : The Natural Philosopher 15 сен 23 14:00:02
Тема : Re: Weird code crash
----------------------------------------------------------------------------------
@MSGID: <wwvpm2jk8ji.fsf@LkoBDZeT.terraraq.uk>
f4e7aa08
@REPLY: 1@dont-email.me> f9a7c029
@REPLYADDR Richard Kettlewell
<invalid@invalid.invalid>
@REPLYTO 2:5075/128 Richard Kettlewell
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<wwvpm2jk8ji.fsf@LkoBDZeT.terraraq.uk>
1@dont-email.me>53kqz@news.chiark.greenend.org.uk>
i.fsf@LkoBDZeT.terraraq.uk> 1@dont-email.me><wwvpm2jgagf.fsf@LkoBDZeT.terraraq.uk>
1@dont-email.me>
@TZUTC: 0100
@PID: Gnus/5.13 (Gnus v5.13) Emacs/27.1
(gnu/linux)
@TID: FIDOGATE-5.12-ge4e8b94
The Natural Philosopher <tnp@invalid.invalid> writes:
> On 15/09/2023 08:30, Richard Kettlewell wrote:
>> The Natural Philosopher <tnp@invalid.invalid> writes:
>>> I am not sure valgrind would actually help unless it failed.
>> It`s extremely good at identifying memory corruption even in cases
>> where that doesn`t immediately lead to a crash; that`s what it`s for.
>> But if it doesn`t, you leave it running until the crash happens.
>
> Well that is an option for sure.
>
>> Up to you, of course, whether you use the tools available, or debug with
>> one hand tied behind your back.
>
> Tell me in what way a corrupted - say - libc file, or a faulty bit of
> memory would show up in the kernel logs?
Very dependent on the nature of the corruption. But you`ve already told
us there`s nothing in the kernel logs.
Anyway, not responsible for advice not taken.
--
https://www.greenend.org.uk/rjk/
--- Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
* Origin: terraraq NNTP server (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441