Eero
Am 13.04.2019 um 09:43 schrieb Eero Tamminen:
Hi,
On 4/12/19 9:52 AM, Michael Schmitz wrote:
Am 12.04.2019 um 11:03 schrieb Eero Tamminen:
[...]
* Stack is always shown, but call trace following it is always empty.
Is call trace explicitly disabled for m68k task list?
No, must be a 030 thing. The output on 060 does show a call trace (at
least for normal processes).
Ok, that's one more bug.
No, that's not a bug. Call trace only prints addresses on the stack that
look like they _might_be from the kernel code segment, along with
function name and offset. These addresses may mean something entirely
different in the context of a user space process, as Andreas pointed out.
The VM layout of the 030 and 060 machines is different, so addresses
from the kernel code segment are quite rare on my 030 (but do appear
occasionally).
Cheers,
Michael
