Custom Query (1030 matches)
Results (349 - 351 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #364 | fixed | IA32 port: SIGTRAP on access to 3D array | ||
| Description |
Welcome to Clozure Common Lisp Version 1.3-dev-r11220M (LinuxX8632)! ? (let ((a (make-array (list 100 100 100)))) (aref a 3 3 3)) Program received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 0xb7c13b90 (LWP 10379)] 0x080560c9 in ?? () 1: x/i $pc 0x80560c9: lea 0x0(%esi,%eiz,1),%esi Current language: auto; currently asm (gdb) bt #0 0x080560c9 in ?? () #1 0x08053345 in _SPFret1valn () at ../x86-spentry32.s:928 #2 0x1434f755 in ?? () #3 0x14920406 in ?? () #4 0xb7aaedd8 in ?? () #5 0x00000004 in ?? () #6 0xfffffffc in ?? () #7 0xb7aaee10 in ?? () #8 0x00000004 in ?? () #9 0x00000000 in ?? () Running on 32-bit Linux. |
|||
| #332 | fixed | IDE shouldn't store CCL directory in preferences | ||
| Description |
It's generally proven to be a bad idea to store the CCL directory in the preferences database. I think that the current thinking is that the CCL directory for a bundled IDE should be initialized in each session to the directory which contains the bundle, and that .dmg distributions should include the .app inside CCL. If someone wants to move the bundle outside of that location, having some mechanism to set the CCL directory for the duration of the current session might be useful (as might be some feedback that indicates that the current setting doesn't look valid.) Viewing the CCL directory as a persistent global preference creates more problems than it solves (e.g., the persistent preference might point to a stale installation and doesn't generally support environments where different IDE versions are installed, etc.) The proposed default (using the parent directory of the application bundle) is consistent with how the IDE is built and likely to be distributed. |
|||
| #237 | fixed | IDE wedges trying to navigate within string | ||
| Description |
In a new buffer, enter (foo "bar then place the insertion point after the quotes and press, e.g., c-m-f. IDE will wedge and has to be killed. I think the problem is that generally, hemlock code isn't prepared to navigate inside strings (valid-spot is nil), but much of the time it doesn't actually check for it so in some cases it just goes into infinite loops. |
|||
