Custom Query (1030 matches)
Results (889 - 891 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #68 | worksforme | NS out of bounds errors while in the editor | ||
| Description |
The first time I ran the IDE, I did (apropos "INIT") and then was mousing around in the listener trying to figure out why the display was so weird (which I eventually narrowed down to issues reported in tickets #66 and #67). I clicked around, did incremental searches, and resized the window - I don't think I did anything else. Anyway, I noticed a bunch of "index beyond array bounds" messages in the terminal window. I saved the terminal output and have attached it here. At the time I thought my lisp was fried so I quit and restarted, and have been unable to duplicate this since then, but am reporting it for the record, in case the backtraces contain enough information to figure out what was going on... |
|||
| #71 | worksforme | Backtrace lines meaninglessly editable | ||
| Description |
double-clicking on a line in backtrace lets you edit it, but it doesn't really mean anything (it restores it immediately upon exit) |
|||
| #81 | worksforme | Listener marks get confused | ||
| Description |
Now that I'm doing more testing/debugging, I find the listener very often gets in a state where hitting return reports Hemlock error "Marks in different buffers have no relation", and the only recourse is to kill the listener (not fun if you have state in a breakloop). I don't have a specific repeatable case, but because of ticket:80 I'm doing a lot of copying and pasting between the listener and editor buffers, and that might have something to do with it. (F04E4B90) : 0 (REPORT-CONDITION-IN-HEMLOCK-FRAME #<SIMPLE-ERROR #xC417CD6> #<HEMLOCK-LISTENER-FRAME <HemlockListenerFrame: 0x2871400> (#x2871400)>) 528
|
|||
