[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug#802593: gcl: FTBFS on hurd-i386

From: Svante Signell
Subject: Re: Bug#802593: gcl: FTBFS on hurd-i386
Date: Mon, 26 Oct 2015 15:07:43 +0100

On Fri, 2015-10-23 at 12:00 +0200, Svante Signell wrote:
> On Thu, 2015-10-22 at 10:59 -0400, Camm Maguire wrote:
> > Greetings, and thanks again for your work on this!
> > 
> > Svante Signell <svante.signell@gmail.com> writes:
> > 

> > > maxima still FTBFS at the same place.
> > >
> > > Seems like there are errors when running gcl for both packages:
> > > task(9610) decreasing a bogus port 1701869637 by 1, most probably a bug.
> > 
> > Interesting.  My general experience has been lockups almost impossible
> > to debug and do anything but a kill -9.

> I managed to create a batch version, see attached maxima_commandline,
> and got an rpctrace (not attached, too big) and a gdb backtrace
> (maxima_gdb.txt). Seems like the bugs are in the memory protection
> parts.

Here is what the gnumach kernel debugger gave:
With the kernel debugger enabled for mach_port_deallocate_debug in
static volatile boolean_t mach_port_deallocate_debug = TRUE;

ps -feMw|grep 1125
     srs  1125  1113

Copied freely from the console output:
task ...nixport/saved_ansi_gcl(1125) decreasing a bogus port 877799456,
most probably a bug.
Debugger invoked: mach_port_mod_refs
Kernel Breakpoint trap, eip 0x801208f4
Stopped at softDebugger+0x13: int $3

trace/tu gave the same result.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]