Custom Query (1030 matches)
Results (232 - 234 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11 | fixed | hand-rolled :darwin64-thread-state64 struct isn't mis-aligned, but should be. | ||
| Description |
Apple has decided that renaming some structures dealing with thread contexts and the fields in those structures would help to ensure compatibility with some C standard or other; the names of these fields therefore depend on what header files one looks at (and what -preserve-broken-legacy-behavior options are in effect.) Lisp code occasionally needs to poke around in these structures, and therefore defines its own set of record types with its own field names "manually". The manual definition of :darwin-ppc-thread-state64 in ccl/level-1/ppc-trap-support.lisp has been wrong; the structure is defined with #pragma pack(4) in effect, so some 64-bit fields that should be misaligned are actually (and incorrectly) naturally aligned. One consequence of this is that backtrace doesn't work on darwinppc64 in some contexts, e.g., after a keyboard interrupt. There may be other consequences, as well. |
|||
| #18 | fixed | undefined-function call: arglist is wrong, restart may not work | ||
| Description |
;;; Assume that BAR is not fboundp. (bar 1 2 3 4 5) Error: Undefined function BAR called with arguments (0 <random> 3 4 5) Something is failing to account for the fact that there's now a return address on the stack. |
|||
| #22 | fixed | The utf-8 character-encoding's LENGTH-OF-MEMORY-ENCODING-FUNCTION returns the wrong answer | ||
| Description |
The variable "nchars" is incremented both in a DO* step form and in the body. |
|||
