Greetings!

Aurelien Chanudet <[EMAIL PROTECTED]> writes:

> > Beyond the axiom issue discussed below, some acl2
> > users at the
> > University of Texas are running into difficulties
> > with the mac code
> > when making very large images.  Would you have a
> > chance to try to
> > build ACL2 with maxpages doubled, quadrupled, and
> > even multiplied by 8
> > if you OS allows?  Please let me know if you have
> > some time to
> > investigate this.  I can send you more information
> > if so.
> 
> What version of ACL2 and gcl are these people using ?
> Will try to give this a look as time permits. By the
> way, what's the status of SGC on the Mac now ? There
> have been some recent issues as far as I remember.
> 

Aurelien, I know life is likely very hectic at the moment, but if by
chance you happen to be able to look into this with the newly created
branch Versin_2_6_7pre in the next few days, that would be fantastic!
Trying to move this out before my own schedule closes in ....


Take care,


> > What dedication!  Is this a known issue on the Mac? 
> > Any help from the
> > gdb developers?
> 
> This is a known issue on the Mac, albeit one that
> interests no one but me (for understandable reasons, I
> feel it way more confortable to debug SGC in GCL using
> gdb than using printf debugging). Basically, attaching
> gdb to a process, say GCL, which handles segfaults on
> its own, makes it impossible for the signal handler to
> be called. Gdb will simply refuse to pass the
> exception to the program. This is due to the way
> traditionnal Unix signals are handled in MacOSX's Mach
> kernel. Traditionnal signals are handled by a BSD
> layer which gdb bypasses... 
> 
> > I'm not sure what you mean here.  Its in the CVS
> > head tree (aka 2.7.0)
> > to my understanding.  Should I post it to the
> > website on the errata
> > page?  
> 
> It must be fine then. I must confess I'm not "CVS
> savvy". I just wanted to make sure that the file can
> be retrieved when using the basic "cvs login / cvs co"
> sequence.
> 
> > 1) Add reloc records for any symbols relocated to a
> > dlopened library
> >    in a given session, together with whatever
> > section is also needed
> >    to indicate that the image is (now permanently)
> > dynamically linked
> >    against the lib.
> >
> > 2) Merge gprof section info from any loaded .o files
> > into the final
> >    saved image so that profiling will work without
> > having to generate
> >    a fresh image with ld.
> 
> Under what form are gprof information stored ?
> 
> 
>       
>       
>               
> ___________________________________________________________________________________________________
> Le nouveau Yahoo! Messenger est arriv� ! D�couvrez toutes les nouveaut�s pour 
> dialoguer instantan�ment avec vos amis. A t�l�charger gratuitement sur 
> http://fr.messenger.yahoo.com 
> 
> 
> 
> _______________________________________________
> Gcl-devel mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/gcl-devel
> 
> 
> 

-- 
Camm Maguire                                            [EMAIL PROTECTED]
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah


_______________________________________________
Gcl-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gcl-devel

Reply via email to