| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | MEX VM issues |
BJ> I know I've seen it reported that the MEX virtual BJ> machine was broken. I think I've now updated to BJ> the version of Maximus directly out of the source BJ> forge site (plus the files in max-3.03-etc.tar.gz), BJ> but I'm not sure.... BJ> Is there currently someone working on the MEX VM? BJ> What has already been tried concerning the MEX VM? I'm looking at the MEX VM on-and-off -- it's been frustrating me. The only changes which ave made it into the CVS versions of max is a modification of the grammar so that it will compile correctly under real yacc (as opposed to GNU bison). The problem is that for some reason, MEX is dereferencing pointers to unallocated memory when its trying to pull stuff from its heap. I originall through the problem was that Scott was coercing pointers into 32 bit scalars and back, but I have since tested under a 32-bit platform (sparc) and it still blows up. Bascially, it's understand-the-code-then-hit-the-debugger time. Wes --- Maximus/2 3.01* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) SEEN-BY: 633/267 270 @PATH: 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.