|
In my previous job I couldn't attach a debugger because a) the SoC didn't have enough free pins for an UART unless I disabled some important functionality, and b), parts of the board could potentially literally catastrophically fail if the execution stopped in an importune moment. I didn't have access to printfs either though, had to do with debug registers.
|
#
¿
Oct 20, 2019 11:49
|
|
|
|
| # ¿ May 16, 2024 17:17 |
|
|
and by "enough" I mean any
|
|
#
¿
Oct 20, 2019 11:55
|
|
|
Poopernickel posted:I'm writing a kernel module right now, and printk is way easier than trying to gdb that poo poo oh yeah I forgot about that, for kernel modules printk is a godsend e: though I'm pretty sure it's not the proper way to debug a kernel module, it would be using a remote debugger I think Private Speech fucked around with this message at 00:14 on Oct 25, 2019 |
|
#
¿
Oct 25, 2019 00:05
|
|
|
The Management posted:just stop all cores with jtag and debug, what’s the problem? if it's drivers for an x86/amd64 linux then that's kinda not always an option, but you can get a remote serial debug interface set up, it's just a giant pain e: windows driver debugging is ime actually a bit easier, but the inability to read through the kernel source sucks Private Speech fucked around with this message at 03:06 on Oct 25, 2019 |
|
#
¿
Oct 25, 2019 02:53
|
|