Reply to thread

Message

<blockquote data-quote="MacDulles" data-source="post: 1611476" data-attributes="member: 334921">What I have learned is that there is *no* laymen's code identification corresponding to * problem* or *error source. It's all couched in binary relative language that offers no *clear* value judgement of errant code flagging that designates the presence of a *known* kernal panic trigger already on path. To my right-brained/left-handed mindcan't *known* code paths to disaster be traced&nbsp; with more illustrary code-pattern indentifiers., warning flags that alert a debugger program which already is programmed to *know* what to hunt down as errant kernal panic triggers that, if followed to their conclusion , will trigger kernal panic. And if my attempt at description reads as so much tortured English gobbilty-gook then please feel my pain over poor defining of what amounts to Martian code to me.&nbsp;Makes me wish that I could let a cursor hover over any line of code and wait for some defining passage, or link to one , to appear in a window just beneath it . ( ie: If you see this here then that may mean possible trouble leading to a kernal panic crash-path) I believe you get my plain layman's English drift.</blockquote>

[QUOTE="MacDulles, post: 1611476, member: 334921"] What I have learned is that there is *no* laymen's code identification corresponding to * problem* or *error source. It's all couched in binary relative language that offers no *clear* value judgement of errant code flagging that designates the presence of a *known* kernal panic trigger already on path. To my right-brained/left-handed mind can't *known* code paths to disaster be traced with more illustrary code-pattern indentifiers., warning flags that alert a debugger program which already is programmed to *know* what to hunt down as errant kernal panic triggers that, if followed to their conclusion , will trigger kernal panic. And if my attempt at description reads as so much tortured English gobbilty-gook then please feel my pain over poor defining of what amounts to Martian code to me. Makes me wish that I could let a cursor hover over any line of code and wait for some defining passage, or link to one , to appear in a window just beneath it . ( ie: If you see this here then that may mean possible trouble leading to a kernal panic crash-path) I believe you get my plain layman's English drift. [/QUOTE]

Verification

Name this item 🌈