Welcome, Guest. Please login or register.

Author Topic: Aros blowing up  (Read 3569 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Georg

  • Jr. Member
  • **
  • Join Date: Feb 2002
  • Posts: 90
    • Show all replies
Re: Aros blowing up
« on: November 29, 2003, 12:29:52 PM »
This GURU seems to come from input.device or
unixio.hidd (I think, having scanned the exe for
this alert numbers). First try running AROS with
some more memory:

  ./aros -m 64

Gives it 64 MByte of RAM.

If this doesn't help recompile the source with debugging
enabled:

   make clean
   ./configure --enable-debug
   make

Then run AROS through the GNU debugger "gdb":

   cd bin/linux-i386/AROS
   gdb aros

Inside gdb enter:

  run -m 64

Then when it crashes do a backtrace by typing

  bt

What output does the backtrace give?
 

Offline Georg

  • Jr. Member
  • **
  • Join Date: Feb 2002
  • Posts: 90
    • Show all replies
Re: Aros blowing up
« Reply #1 on: November 29, 2003, 12:39:51 PM »
Ah, and if after the "run" in gdb it gets interrupted through a (mysterious. no idea where coming from)
SIGTRAP type "cont" to make it continue from where
it was interrupted.

BTW: At what depth is your X11 Server running?