Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

UpdateStringProc crash with tcl8.6 on AIX

90 views
Skip to first unread message

Carol Sandstrom

unread,
Aug 7, 2015, 4:09:27 PM8/7/15
to
I am building tcl8.6 on AIX using native AIX tools (xlc_r) and a very simple configuration:

env CC=/usr/local/packages/vac_remote/9-sept2008/usr/vacpp/bin/xlc_r
CXX=/usr/local/packages/vac_remote/9-sept2008/usr/vacpp/bin/xlC_r
./configure --prefix=/home/csandstr/programs --enable-threads

The build and install appear to go just fine, but when I fire up the tclsh I get this:

/scratch/csandstr/programs/bin/tclsh8.6
UpdateStringProc should not be invoked for type
Abort process (core dumped)


This same configuration and build on the same machine works fine for tcl8.5, but not for any of the tcl8.6's I've tried (8.6.0, 8.6.3, 8.6.4).

Any suggestions?

Thanks
Carol

Andreas Leitgeb

unread,
Aug 9, 2015, 6:33:32 AM8/9/15
to
Is building with gcc an option?

I've got tcl8.6.3 and tclX 8.4.1 built with gcc and running
fine on AIX, although the build-process was a bit bumpy.

Carol Sandstrom

unread,
Aug 13, 2015, 1:45:59 PM8/13/15
to
Hmm ... actually that is worth a shot. Thanks for the suggestion. I'd still be interested in hearing if anyone has encountered the UpdateStringProc problem, though!

Carol Sandstrom

unread,
Aug 17, 2015, 12:22:22 PM8/17/15
to

> The build and install appear to go just fine, but when I fire up the tclsh I get this:
>
> /scratch/csandstr/programs/bin/tclsh8.6
> UpdateStringProc should not be invoked for type
> Abort process (core dumped)
>

I configured and built Tcl with gcc and got the same outcome! So it's not a compiler issue.

Carol Sandstrom

unread,
Aug 24, 2015, 2:55:36 PM8/24/15
to
I added --enable-symbols to the configure string and the problem was resolved.


env CC=/usr/local/packages/vac_remote/9-sept2008/usr/vacpp/bin/xlc_r
CXX=/usr/local/packages/vac_remote/9-sept2008/usr/vacpp/bin/xlC_r
./configure --prefix=/home/csandstr/programs --enable-threads --enable-symbols

Christian Gollwitzer

unread,
Aug 24, 2015, 4:19:56 PM8/24/15
to
Am 24.08.15 um 20:55 schrieb Carol Sandstrom:
> I added --enable-symbols to the configure string and the problem was
> resolved.
>
Unlikely. Either it is shadowed by the presence of additional pages, or
it is a bug in the compiler when optimizations are enabled.
--enable-symbols, among others, disables optimization when Tcl is
compiled. You are now running an unoptimized build.

> env CC=/usr/local/packages/vac_remote/9-sept2008/usr/vacpp/bin/xlc_r
> CXX=/usr/local/packages/vac_remote/9-sept2008/usr/vacpp/bin/xlC_r
> ./configure --prefix=/home/csandstr/programs --enable-threads
> --enable-symbols

Christian


Andreas Kupries

unread,
Oct 10, 2015, 4:08:30 AM10/10/15
to

Carol Sandstrom <carolsa...@gmail.com> wrote:
> I am building tcl8.6 on AIX using native AIX tools (xlc_r) and a very simple configuration:
> env CC=/usr/local/packages/vac_remote/9-sept2008/usr/vacpp/bin/xlc_r
> CXX=/usr/local/packages/vac_remote/9-sept2008/usr/vacpp/bin/xlC_r
> ./configure --prefix=/home/csandstr/programs --enable-threads
> The build and install appear to go just fine, but when I fire up the tclsh I get this:
> /scratch/csandstr/programs/bin/tclsh8.6
> UpdateStringProc should not be invoked for type
> Abort process (core dumped)

Just starting the tclsh generates the crash ?

Have you tried to build with symbols ?
The crash should then produce a stack trace more suitable to
debugging, with proper function names.

This should be submitted to the ticket trackers at

http://core.tcl.tk/tcl/

Might also be worthwhile to build not just with symbols, but also the
integrated memory debugging active.

--enable-symbols=all

If we are lucky whatever memory smash causes this will then be caught
in that net.

--
So long,
Andreas Kupries <akup...@shaw.ca>
<http://core.tcl.tk/akupries/>
Developer @ HP Enterprise

Tcl'2015, Oct 19-23, Manassas, VA, USA, http://www.tcl.tk/community/tcl2015/
-------------------------------------------------------------------------------
0 new messages