ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
apritzel has quit [Ping timeout: 244 seconds]
Misotauros has quit [Ping timeout: 258 seconds]
Pali has quit [Ping timeout: 244 seconds]
bps has joined #armlinux
bps has quit [Changing host]
bps has joined #armlinux
bps has quit [Remote host closed the connection]
mripard has quit [Ping timeout: 246 seconds]
mripard has joined #armlinux
ravan has joined #armlinux
ravan has quit [Ping timeout: 244 seconds]
ravan has joined #armlinux
ravan has quit [Client Quit]
Pali has joined #armlinux
vvlad has quit [Quit: Leaving]
Nact has quit [Quit: Konversation terminated!]
apritzel has joined #armlinux
Misotauros has joined #armlinux
apritzel has quit [Ping timeout: 244 seconds]
nsaenz has quit [Remote host closed the connection]
ardb has quit [Quit: Leaving.]
ardb has joined #armlinux
nsaenz has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
frieder has joined #armlinux
nsaenz has quit [Remote host closed the connection]
frieder has quit [Remote host closed the connection]
apritzel has joined #armlinux
apritzel has quit [Ping timeout: 260 seconds]
headless has joined #armlinux
headless has quit [Quit: Konversation terminated!]
seL4 has joined #armlinux
<seL4> anybody know why gdb is adding 2 to current instruction for pc instead of 4 in thumb mode for arm?
<seL4> r0 is 0xbeffffd8 instead of 0xbeffffda
<jn> because thumb instructions can be and often are 2 bytes long, that's the point of thumb
Amit_T has joined #armlinux
<jn> according to gdb's built-in disassembler, the instruction at 0xbeffffd6 is 2 bytes long
<jn> (i might be missing something though)
<seL4> oops I sent to wrong channel
<seL4> yes, so its pc + 2 thumb instructions = pc + 4?
<seL4> yeah, its in thumb mode
<seL4> 0xbeffffce (current instruction) + 4 + 8 would be 0xbeffffda (pc)
<seL4> but r0 is 0xbefffd8
<seL4> *0xbeffffd8
<jn> i don't know how gdb handle's ARM's quirk that reading pc results in a value advanced by two instructions
<seL4> yeah I tried on a different thing and it does add 4 to current instruction to get pc
<seL4> but I'll ask in gdb channel
Amit_T has quit [Remote host closed the connection]
nsaenz has joined #armlinux
nsaenz has quit [Remote host closed the connection]
apritzel has joined #armlinux
elastic_dog has quit [Ping timeout: 264 seconds]
elastic_dog has joined #armlinux
dliviu has quit [Quit: Going away]
dliviu has joined #armlinux
ardb has quit [Quit: Leaving.]
seL4 has quit [Remote host closed the connection]
Pali has quit [Ping timeout: 244 seconds]