> I now build oskit directly in its top level dir, not in build, to
> simplify the remote debugging.
Do not expect this to work. This is true in many packages.
Separate build directories are a good thing.
ATTN: Marcus, Roland
Hi,
Haven't had the inertia to do it today, but I'll see if I can get
your info compiled tomorrow. On a whim, I wondered if my
scsi bios was the culprit (last week I booted from hda but
now I boot from sda for many reasons). I toggled my bios boot
options and tried it under ide
On Sun, Mar 03, 2002 at 11:38:38PM -0500, B. Douglas Hilton wrote:
>Program received signal SIGSEGV, Segmentation Fault.
>0x00156173 in trap_from_kernel ()
What we always need is a complete backtrace (bt full), the register settings
(info reg) and the assembler code in that location (x/40i
> Sadly, it's been instant reboots all day long. I finally got it
> to crash at a trap now though on my latest compile. Here
> is the info I have gleaned from my debugger:
You need to step more slowly. Do "display/i $pc" and then use "si" (short
for "stepi") instead of regular "step". Then you w
Hi,
I worked all day attempting to recompile oskit and oskit-mach
and have yet to duplicate my astounding stroke of luck last
weekend where I managed to get oskit-mach to boot.
Sadly, it's been instant reboots all day long. I finally got it
to crash at a trap now though on my latest compile. Here
i
5 matches
Mail list logo
