Re: Got my name in the list

MT builds successful only with --enable-portability but running clisp
binary segfaults. Presently debugging the binary to go through the code and
find where is the problem. Do suggest me if there is a better way to debug
as I am using gdb using multiple windows in Emacs and some variables are
optimized out so its a bit hard to look into it. Still don't know how to
look into optimized variables.

On Sat, May 6, 2017 at 5:43 AM, Don Cohen <
[email protected]> wrote:

> Vladimir Tzankov writes:
>  > Hey Compro,
>  >
>  > Let's outline the next steps.
>  > Here is a list off the top of my head - any suggestions and comments
>  > are welcomed.
>  >
>  > * build MT (POSIX_THREADS) and ensure 'check-tests' passes.
>
> Actually, this is likely to be a challenge already in the current state.
> As I've posted recently, this fails for many of the memory models, inc.
> whichever is the default on my current system (linux).
> I suggest starting with Makefile.devel (is that part of the hg source?),
> finding the line that says
>  # Options to pass to configure
> and changing the next line to
>  MULTIBUILD_OPTIONS =  --with-threads=POSIX_THREADS
> storing the result as Makefile.develMT
> then
>  make -f Makefile.develMT -k multibuild-porting64-gcc
> in order to at least find SOME way to build MT.
>
> I'd also appreciate if someone could make most or all of the
> memory models build, as they used to only a few months ago.
>
> BTW I have recently run across some fairly reliable ways to cause
> MT bugs, some involving locking and some crashing.
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel