<Ermine>
today in linux desktop news: my keyboard and mouse are not working on kernal 6.16.3
TkTech has quit [Ping timeout: 256 seconds]
TkTech8 is now known as TkTech
<indraj>
sounds like an average day on linux
<indraj>
I ran into something similar with my network card a few years ago, I ended up having to swap it out after some bug reports went nowhere
Turn_Left has joined #osdev
Left_Turn has quit [Ping timeout: 244 seconds]
EmanueleDavalli has quit [Quit: Leaving]
Burgundy has left #osdev [#osdev]
<heat>
Ermine: post dmesg
pitust has quit [Server closed connection]
pitust has joined #osdev
Left_Turn has joined #osdev
msv has quit [Remote host closed the connection]
Turn_Left has quit [Ping timeout: 244 seconds]
Burgundy has joined #osdev
k0valski18891621 has quit [Server closed connection]
Left_Turn has quit [Read error: Connection reset by peer]
Ram-Z has quit [Server closed connection]
Ram-Z has joined #osdev
goliath has joined #osdev
Left_Turn has joined #osdev
eluks has quit [Server closed connection]
eluks has joined #osdev
noeontheend has quit [Server closed connection]
noeontheend has joined #osdev
Left_Turn has quit [Read error: Connection reset by peer]
Left_Turn has joined #osdev
sebastiencs has quit [Server closed connection]
<Ermine>
heat: nah, I'm having more fun dealing with arm board on which kernal crashes early
sebastiencs has joined #osdev
<clever>
Ermine: ive had similar problems, it hangs right as its switching from earlycon to ttyAMA0, but if i modify any code, it crashes at a different place!
<Ermine>
in my case, it's probably because i haven't built arm trusted firmware
<clever>
Ermine: yeah, looks like its trying to use PSCI to contact the ATF
<zid>
So it can land at LAX
Left_Turn has quit [Ping timeout: 256 seconds]
pabs3 has joined #osdev
ring0_starr has joined #osdev
<nikolar>
Why would it want to land at lax though
<Ermine>
why not
<zid>
because it's the only airport code I can remember
msv has joined #osdev
dude12312414 has joined #osdev
<kof673>
in soviet lax, alcohol tobacco firearms bureau finds you :D
dude12312414 has quit [Quit: THE RAM IS TOO DAMN HIGH]
<nikolar>
Ermine: because that would mean you'd want to go to US
goliath has quit [Quit: SIGSEGV]
netbsduser` has joined #osdev
TkTech4 has joined #osdev
TkTech has quit [Ping timeout: 256 seconds]
TkTech4 is now known as TkTech
<Ermine>
oh
Left_Turn has joined #osdev
Turn_Left has quit [Ping timeout: 244 seconds]
Turn_Left has joined #osdev
Left_Turn has quit [Ping timeout: 244 seconds]
Pixi has quit [Server closed connection]
Pixi has joined #osdev
EmanueleDavalli has joined #osdev
chiselfuse has joined #osdev
xenos1984 has quit [Ping timeout: 252 seconds]
xenos1984 has joined #osdev
xenos1984 has quit [Ping timeout: 248 seconds]
xenos1984 has joined #osdev
Turn_Left has quit [Read error: Connection reset by peer]
Left_Turn has joined #osdev
EmanueleDavalli has quit [Ping timeout: 256 seconds]
EmanueleDavalli has joined #osdev
eluks has quit [Remote host closed the connection]
eluks has joined #osdev
EmanueleDavalli has quit [Remote host closed the connection]
EmanueleDavalli has joined #osdev
TkTech5 has joined #osdev
TkTech has quit [Ping timeout: 256 seconds]
TkTech5 is now known as TkTech
FreeFull has quit []
<chiselfuse>
do debuggers guess the base address of loaded images if i attach a ptrace to an already existing process in order to map the symbols assigned to the virtual address space of the elf to the real one?
<chiselfuse>
for DYN elfs at least
<chiselfuse>
they just look at /proc/maps and guess where the base address is? or is there a more confident way
<heat>
platform dependent
<heat>
on linux they snoop dynamic linker structs
<heat>
see _dl_debug_addr and _dl_debug_state
eluks has quit [Remote host closed the connection]
eluks has joined #osdev
<chiselfuse>
heat: okay so how do you in turn find _dl_debug_addr? and besides that, how do debuggers find information of loaded images (i assume this is what you can get via _dl_debug_addr) for images with no INTERP?
<heat>
ELF symbols
<heat>
and for images with no interp you can eyeball it, yes
<heat>
at least that's what they do for coredumps
<chiselfuse>
so for EXECs i imagine it's easy, but for DYNs, you just have to guess the base address, right?
<heat>
sure
<heat>
i mean, i would read the code if i were you
<chiselfuse>
of something like gdb?
<heat>
yeah
<heat>
or lldb
<heat>
(I think lldb is a little less spaghetti)
<chiselfuse>
good idea yea
freakazoid332 has quit [Ping timeout: 260 seconds]
<zid>
gef➤ pf $rsp --lang c --bitlen 8
<zid>
unsigned char buf[256] = {0x18, 0xdf, 0xff,
<zid>
gef has weird features like this
<zid>
but I can't figure out how to get a hexdump display