Re: re-enabling debugging of 32 bit processes with 64 bit debugger

m...@eterna.com.au (matthew green) writes: >i fully support making debugging work. that means debugging >32 bit apps on 64 it kernels, and also, eventually?, using >a 32 bit debugger on 64 bit kernel. Can we prevent a 64bit kernel to dump 64bit registers for 32bit userland processes ? -- --

Re: re-enabling debugging of 32 bit processes with 64 bit debugger

In article , Michael van Elst wrote: >m...@eterna.com.au (matthew green) writes: > >>i fully support making debugging work. that means debugging >>32 bit apps on 64 it kernels, and also, eventually?, using >>a 32 bit debugger on 64 bit kernel. > >Can we prevent a 64bit kernel to dump 64bit regist

Re: re-enabling debugging of 32 bit processes with 64 bit debugger

chris...@astron.com (Christos Zoulas) writes: >We can fill them completely with 0 as we pad with 0 the 32 bit >part of the 64 bit registers that does not exist in a 32 bit >process. The corefile pretends to be a 32bit file, so the register section should probably be similar to a coredump of a 32b

Re: re-enabling debugging of 32 bit processes with 64 bit debugger

In article , Michael van Elst wrote: >chris...@astron.com (Christos Zoulas) writes: > >>We can fill them completely with 0 as we pad with 0 the 32 bit >>part of the 64 bit registers that does not exist in a 32 bit >>process. > >The corefile pretends to be a 32bit file, so the register >section sho

Re: re-enabling debugging of 32 bit processes with 64 bit debugger

On 01.07.2019 16:01, Christos Zoulas wrote: > In article , > Michael van Elst wrote: >> chris...@astron.com (Christos Zoulas) writes: >> >>> We can fill them completely with 0 as we pad with 0 the 32 bit >>> part of the 64 bit registers that does not exist in a 32 bit >>> process. >> >> The corefi

Re: re-enabling debugging of 32 bit processes with 64 bit debugger

On Mon, 1 Jul 2019 at 10:06, Kamil Rytarowski wrote: > > On 01.07.2019 16:01, Christos Zoulas wrote: > > In article , > > Michael van Elst wrote: > >> chris...@astron.com (Christos Zoulas) writes: > >> > >>> We can fill them completely with 0 as we pad with 0 the 32 bit > >>> part of the 64 bit r

Re: re-enabling debugging of 32 bit processes with 64 bit debugger

On 01.07.2019 17:06, Andrew Cagney wrote: > On Mon, 1 Jul 2019 at 10:06, Kamil Rytarowski wrote: >> >> On 01.07.2019 16:01, Christos Zoulas wrote: >>> In article , >>> Michael van Elst wrote: chris...@astron.com (Christos Zoulas) writes: > We can fill them completely with 0 as we pa

kmem_alloc() vs. VM_MIN_KERNEL_ADDRESS

Sometimes kmem_alloc() returns an address below VM_MIN_KERNEL_ADDRESS, something like kmem_alloc() -> 0xaba25800a5a8 with VM_MIN_KERNEL_ADDRESS 0xad80 It doesn't happen after every reboot and breaks dtrace which treats the region 0.. VM_MIN_KERNEL_ADDRESS as toxic. How could

Re: kmem_alloc() vs. VM_MIN_KERNEL_ADDRESS

Le 01/07/2019 à 19:40, J. Hannken-Illjes a écrit : Sometimes kmem_alloc() returns an address below VM_MIN_KERNEL_ADDRESS, something like kmem_alloc() -> 0xaba25800a5a8 with VM_MIN_KERNEL_ADDRESS 0xad80 It doesn't happen after every reboot and breaks dtrace which treats the