This GDB was configured as "ipc-linux-gnu" See notes on building TclPro. I first ran into this segfault with tcl 8. Here is the back trace from a tclsh8. From the pkgIndex file for this byte compiler:
| Uploader: | Dailkis |
| Date Added: | 20 April 2004 |
| File Size: | 50.33 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 42173 |
| Price: | Free* [*Free Regsitration Required] |
From the pkgIndex file for 1.44 byte compiler: See notes on building TclPro. The lines below provide: This GDB was configured as "ipc-linux-gnu" There is absolutely no warranty for GDB. Failed to read a valid object file image from memory.
I subsequently checked with 8. What tbcload are you using to load this bytecode? And for those peeking in, version 1. The term 'TclPro' is trademarked. The TclPro debugger is strictly a debugger - it does not contain the ability to edit code and then continue on. Hi Jeff, With respect to: Free forum by Nabble. Uhmm, the rbcload for the missing symbol info was a wrong tclsh library, sorry.
tcl-bugs - [Tcl-bugs] [ tcl-Bugs ] tclsh segfaults upon sourcing byte codes
Don Porter dgp Date: Erik Leunissen eriklns Assigned to: Bugs itemwas opened at Is this a new regression in 8. See Also deployment [ 1 ]Cameron Tbclload personal notes on Tcl compilers includes a section on static analyzers https: TclPro Key for 10 seats 1. The files in this directory require license keys in order to use the development tools e. Don't know about earlier releases.
Category Application Category Debugging. Type "show warranty" for details.
RPM resource libtbcload1.4.so()(64bit)
And this is not a Tcl problem, but rather one with tbcload. TclPro also makes it easy to package and distribute Tcl applications, and it protects source code from copying and alterations. Also available as part of ActiveTcl Pro Studio.
tbcloar Jeffrey Hobbs hobbs Date: Out of Date Priority: From the name of the command and its output procomp, this is a TDK 1. Program terminated with signal 11, Segmentation fault.
[Tcl-bugs] [ tcl-Bugs-2782488 ] tclsh8.5 segfaults upon sourcing 8.4 byte codes
With what are you creating the bytecode? I do not believe so. Can't read pathname for load map: I just tried to reproduce the problem using TDK 5. Instead, one uses a favorite editor, and then start the app over again. Everyone is encouraged to take it to a more appropriate bug reporting mechanism where tbcload's inability tbcloar correctly create bytecode structures can be addressed.
No comments:
Post a Comment