From: Vladimir Zolotykh
Subject: Both still valid #.(SYSTEM:INT-SAP #x3FFFEF0C)....
Date: 
Message-ID: <3CD67F00.4C1B0262@eurocom.od.ua>
I've encountered a strange error during run of some program
(under CMUCL18c , Slackware 8.0)

[GC threshold exceeded with 3,347,112 bytes in use.  Commencing GC.]
[GC completed with 1,378,840 bytes retained and 1,968,272 bytes freed.]
[GC will next occur when at least 3,378,840 bytes are in use.]
Debug: Both still valid #.(SYSTEM:INT-SAP #x3FFFEF0C) #.(SYSTEM:INT-SAP #x20000078) #.(SYSTEM:INT-SAP #x3FFFEA94)
#.(SYSTEM:INT-SAP #x08053303)


Error in function UNIX::SIGSEGV-HANDLER:  Segmentation Violation at #x10148B64.

I have not even smallest idea how I could deal something with it, or
what is the cause for it. Could you help me?

I have seen a backtrace, it didn't clear something for me. Here it is

0] backtrace

0: (UNIX::SIGSEGV-HANDLER #<unavailable-arg>
                          #<unavailable-arg>
                          #.(SYSTEM:INT-SAP #x3FFFE5F0))
1: ("Foreign function call land")
2: ("Foreign function call land")
3: ("Foreign function call land")
4: ("Foreign function call land")
5: (DEBUG-INTERNALS::INVOKE-BREAKPOINT-HOOKS
    (#<Breakpoint QUERY:FUNCTION-START> #<Breakpoint QUERY:FUNCTION-START>)
    #<Code Object "DEFUN QUERY" {4800908F}>
    263)
6: (DEBUG-INTERNALS::HANDLE-BREAKPOINT-AUX
    (#<Breakpoint QUERY:FUNCTION-START> #<Breakpoint QUERY:FUNCTION-START>)
    #<Breakpoint-Data QUERY at 263>
    263
    #<Code Object "DEFUN QUERY" {4800908F}>
    ...)
7: ("Foreign function call land")
8: ("Foreign function call land")
9: ("Foreign function call land")Debug: Both still valid #.(SYSTEM:INT-SAP #x3FFFEF0C) #.(SYSTEM:INT-SAP #x20000078)
#.(SYSTEM:INT-SAP #x3FFFEA94) #.(SYSTEM:INT-SAP #x08053303)
10: ("Foreign function call land")
11: ("Foreign function call land")

0] 

I'm using MaiSQL, so you can see references to its functions.

Thanks in advance

-- 
Vladimir Zolotykh

From: Andy
Subject: Re: Both still valid #.(SYSTEM:INT-SAP #x3FFFEF0C)....
Date: 
Message-ID: <3CD6BA07.5A60AE4A@smi.de>
Hi Vladimir,
sorry i have no doubt whats going wrong. But maybe you should post
the request to the CMUCL mailing list. I don't know if the CMUCL
volunteers
all read this NG.
Best regards
AHz


Vladimir Zolotykh wrote:
> 
> I've encountered a strange error during run of some program
> (under CMUCL18c , Slackware 8.0)
> 
> [GC threshold exceeded with 3,347,112 bytes in use.  Commencing GC.]
> [GC completed with 1,378,840 bytes retained and 1,968,272 bytes freed.]
> [GC will next occur when at least 3,378,840 bytes are in use.]
> Debug: Both still valid #.(SYSTEM:INT-SAP #x3FFFEF0C) #.(SYSTEM:INT-SAP #x20000078) #.(SYSTEM:INT-SAP #x3FFFEA94)
> #.(SYSTEM:INT-SAP #x08053303)
> 
> Error in function UNIX::SIGSEGV-HANDLER:  Segmentation Violation at #x10148B64.
> 
> I have not even smallest idea how I could deal something with it, or
> what is the cause for it. Could you help me?
> 
> I have seen a backtrace, it didn't clear something for me. Here it is
> 
> 0] backtrace
> 
> 0: (UNIX::SIGSEGV-HANDLER #<unavailable-arg>
>                           #<unavailable-arg>
>                           #.(SYSTEM:INT-SAP #x3FFFE5F0))
> 1: ("Foreign function call land")
> 2: ("Foreign function call land")
> 3: ("Foreign function call land")
> 4: ("Foreign function call land")
> 5: (DEBUG-INTERNALS::INVOKE-BREAKPOINT-HOOKS
>     (#<Breakpoint QUERY:FUNCTION-START> #<Breakpoint QUERY:FUNCTION-START>)
>     #<Code Object "DEFUN QUERY" {4800908F}>
>     263)
> 6: (DEBUG-INTERNALS::HANDLE-BREAKPOINT-AUX
>     (#<Breakpoint QUERY:FUNCTION-START> #<Breakpoint QUERY:FUNCTION-START>)
>     #<Breakpoint-Data QUERY at 263>
>     263
>     #<Code Object "DEFUN QUERY" {4800908F}>
>     ...)
> 7: ("Foreign function call land")
> 8: ("Foreign function call land")
> 9: ("Foreign function call land")Debug: Both still valid #.(SYSTEM:INT-SAP #x3FFFEF0C) #.(SYSTEM:INT-SAP #x20000078)
> #.(SYSTEM:INT-SAP #x3FFFEA94) #.(SYSTEM:INT-SAP #x08053303)
> 10: ("Foreign function call land")
> 11: ("Foreign function call land")
> 
> 0]
> 
> I'm using MaiSQL, so you can see references to its functions.
> 
> Thanks in advance
> 
> --
> Vladimir Zolotykh
From: Wolfgang Mederle
Subject: Re: Both still valid #.(SYSTEM:INT-SAP #x3FFFEF0C)....
Date: 
Message-ID: <n5s6ba.jo.ln@DS9.mederle.de>
Vladimir Zolotykh wrote:

> I've encountered a strange error during run of some program
> (under CMUCL18c , Slackware 8.0)
[...]
> Error in function UNIX::SIGSEGV-HANDLER: Segmentation Violation at
> #x10148B64.

It might be a problem with libsafe. I saw errors like this one, also on
a Slack 8 box, when libsafe was installed. Solution: either remove the
libsafe package or remove it and install a more recent version, as the
recent ones come with a config file from which one can exclude apps that
libsafe falsely accuses of segfaulting, like cmucl 18c, or e2fsck.

-- 
Wolfgang Mederle

$BONMOT
From: Vladimir Zolotykh
Subject: Re: Both still valid #.(SYSTEM:INT-SAP #x3FFFEF0C)....
Date: 
Message-ID: <3CD7E188.3448259D@eurocom.od.ua>
Thank you
I'll try this.
Unfortunately, the error isn't highly reproducible.
Sometimes it is sometimes not.
And I don't know for yet the exact circumstances that
being established guarantee its appearance.

Wolfgang Mederle wrote:
> 
> Vladimir Zolotykh wrote:
> 
> > I've encountered a strange error during run of some program
> > (under CMUCL18c , Slackware 8.0)
> [...]
> > Error in function UNIX::SIGSEGV-HANDLER: Segmentation Violation at
> > #x10148B64.
> 
> It might be a problem with libsafe. I saw errors like this one, also on
> a Slack 8 box, when libsafe was installed. Solution: either remove the
> libsafe package or remove it and install a more recent version, as the
> recent ones come with a config file from which one can exclude apps that
> libsafe falsely accuses of segfaulting, like cmucl 18c, or e2fsck.
> 
> --
> Wolfgang Mederle
> 
> $BONMOT

-- 
Vladimir Zolotykh