<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hello,<br>
<br>
I'm grad to hear from you :)<br>
<br>
I checked the source code as you mentioned<br>
<br>
Comparing two archives with sha256 checksum gives;<br>
<br>
70b02347723e463c381a315a3695681f0addb831bb4ba009dc4ec8ea3bf235f6
rpl-4.0.0.prerelease.2.tar.bz2<br>
d7c674f8c45da752531d4250e781e6eb633e09865d572fbf1144c20cbd419827
rpl-4.0.0.prerelease.2.tar.bz2.Oct1<br>
<br>
It's different!<br>
<br>
I've looked into the source code(src/encart.c), and found that
XtDestroyWidget() functions were missing in my archive,<br>
<br>
which I downloaded the source (rpl-4.0.0.prerelease.2.tar.bz2) from
the official RPL/2 web directly before Oct. 1<br>
<pre wrap=""> XtDestroyWidget(pixmap);
XtDestroyWidget(cadre);
XtDestroyWidget(form);
XtDestroyWidget(popup);
XtDestroyWidget(objet_principal);
</pre>
<br>
I don't understand why this happened ;-)<br>
<br>
I have some suggestions regarding this issue,<br>
<br>
It's a good idea to give checksums(i.e, md5) on the official web site,
and <br>
<br>
<br>
Another suggestion is;<br>
<br>
it's also useful to offer some links to access HP RPL document<br>
<br>
For your convenience, <br>
<br>
<a class="moz-txt-link-freetext" href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00554621/c00554621.pdf">http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00554621/c00554621.pdf</a><br>
<br>
or, RPL wiki page<br>
<br>
<a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/RPL_(programming_language)">http://en.wikipedia.org/wiki/RPL_(programming_language)</a><br>
<br>
Thanks a million for your help, and<br>
<br>
I cannot help but appreciate your a great deal of efforts into RPL/2<br>
<br>
Please keep your good work!<br>
<br>
<br>
Best regards,<br>
<br>
Woody Jeon<br>
<br>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:rpl2-request@rayleigh.systella.fr">rpl2-request@rayleigh.systella.fr</a> wrote:
<blockquote
cite="mid:mailman.1.1195124406.21038.rpl2@rayleigh.systella.fr"
type="cite">
<pre wrap="">Envoyez vos messages pour la liste RPL2 à
<a class="moz-txt-link-abbreviated" href="mailto:rpl2@rayleigh.systella.fr">rpl2@rayleigh.systella.fr</a>
Pour vous (dés)abonner par le web, consultez
<a class="moz-txt-link-freetext" href="https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2">https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2</a>
ou, par email, envoyez un message avec 'help' dans le corps ou dans le
sujet à
<a class="moz-txt-link-abbreviated" href="mailto:rpl2-request@rayleigh.systella.fr">rpl2-request@rayleigh.systella.fr</a>
Vous pouvez contacter l'administrateur de la liste à l'adresse
<a class="moz-txt-link-abbreviated" href="mailto:rpl2-owner@rayleigh.systella.fr">rpl2-owner@rayleigh.systella.fr</a>
Si vous répondez, n'oubliez pas de changer l'objet du message afin
qu'il soit plus spécifique que "Re: Contenu du digest de RPL2..."
Thèmes du jour :
1. Access violation (stack overflow) (Woody Jeon)
2. Re: Access violation (stack overflow) (BERTRAND Joël)
----------------------------------------------------------------------
Message: 1
Date: Thu, 15 Nov 2007 12:01:52 +0900
From: Woody Jeon <a class="moz-txt-link-rfc2396E" href="mailto:woody@posdata.co.kr"><woody@posdata.co.kr></a>
Subject: [RPL/2] Access violation (stack overflow)
To: <a class="moz-txt-link-abbreviated" href="mailto:rpl2@rayleigh.systella.fr">rpl2@rayleigh.systella.fr</a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:473BB6A0.2030400@posdata.co.kr"><473BB6A0.2030400@posdata.co.kr></a>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I compiled the prerelease.2 and got a message right after rpl started,
"+++System : Access violation (stack overflow)"
Even though I have no idea this is harmful or not, it doesn't seem a
good sign
Any idea on this?
cheers,
woody
------------------------------------------------------------------------------------------------------------------------------------
$ rpl -i
+++RPL/2 version 4.0.0.prerelease.2 (Monday 10/01/07, 20:46:21 KST)
+++Copyright (C) 1989 to 2006, 2007 BERTRAND Joël
+++This is a free software with absolutely no warranty.
+++For details, type 'warranty'.
+++System : Access violation (stack overflow)
RPL/2>
------------------------------
Message: 2
Date: Thu, 15 Nov 2007 09:54:09 +0100
From: BERTRAND Joël <a class="moz-txt-link-rfc2396E" href="mailto:joel.bertrand@systella.fr"><joel.bertrand@systella.fr></a>
Subject: Re: [RPL/2] Access violation (stack overflow)
To: RPL/2 mailing list <a class="moz-txt-link-rfc2396E" href="mailto:rpl2@rayleigh.systella.fr"><rpl2@rayleigh.systella.fr></a>
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:473C0931.9000300@systella.fr"><473C0931.9000300@systella.fr></a>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Woody Jeon wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I compiled the prerelease.2 and got a message right after rpl started,
"+++System : Access violation (stack overflow)"
Even though I have no idea this is harmful or not, it doesn't seem a
good sign
Any idea on this?
</pre>
</blockquote>
<pre wrap=""><!---->
Yes, I have ;-)
Please try to launch RPL/2 with rpl -is. I think you shouldn't receive
a stack overflow error. Where have you downloaded sources ? This very
minor bug (segfault when a child process ends) was fixed a long time
ago. I have verified that it is fixed in 4.0.0.prerelease.2 on the
official web page.
You can check too that src/encart.c ends by :
XmDestroyPixmap(XtScreen(popup), pixmap_rpl);
XmDestroyPixmap(XtScreen(popup), pixmap_rpl_masque);
XtDestroyWidget(pixmap);
XtDestroyWidget(cadre);
XtDestroyWidget(form);
XtDestroyWidget(popup);
XtDestroyWidget(objet_principal);
if (sigaction(SIGINT, &action_passee, NULL) != 0)
{
(*s_etat_processus).erreur_systeme = d_es_signal;
return;
}
exit(0);
}
else
{
if (sigaction(SIGINT, &action_passee, NULL) != 0)
{
(*s_etat_processus).erreur_systeme = d_es_signal;
return;
}
(*s_etat_processus).erreur_systeme = d_es_signal;
return;
}
}
# endif
return;
}
// vim: ts=4
That being said, it is possible you have found a new bug. In this case,
you can start RPL/2 with (of course in bash ulimit -c unlimited) rpl -id
to avoid signal management.
Regards,
JKB
------------------------------
_______________________________________________
RPL2 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:RPL2@rayleigh.systella.fr">RPL2@rayleigh.systella.fr</a>
<a class="moz-txt-link-freetext" href="https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2">https://www.systella.fr/cgi-bin/mailman/listinfo/rpl2</a>
<a class="moz-txt-link-freetext" href="http://www.systella.fr/~bertrand/rpl2/english.html">http://www.systella.fr/~bertrand/rpl2/english.html</a>
Fin de Lot RPL2, Vol 39, Parution 2
***********************************
</pre>
</blockquote>
<br>
</body>
</html>