home *** CD-ROM | disk | FTP | other *** search
- On Dec 6, 5:06pm, olivier lahaye wrote:
- >
- > Actualy, these beta version (no shared libs) is printing debug informations
- > assuming you've launched it from another console.
- > it seems that was this debug info which crashes #713 closed ite driver.
- > so ite should ignore these message when closed.
- > all debug info will be removed in final version.
- > You can ru Xbsd like this:
- > Xbsd >foo
- > or
- > Xbsd >/dev/null /* for normal usage */
-
- Is the X11R5 server using stdout or stderr? I found that there was one
- line of output sent to stderr, so I had to use:
- Xbsd 2>/tmp/X.err
- (The data printed was just something like "Size: 65???".)
-
- Also, I think the crashes only occur with the cc code. When the ite
- device is closed, it releases some data structures that were set up when
- it was opened. When the cc cursor or putc routines were called, they
- attempted to use those data structures and crashed. [I'm starting to get
- the hang of examining MMU fault panics :-).]
-
- > The code will of course be available when it'll be cleaned
- > (no debug ErroF, ...)
- > You shouldn't blame us for those time delays, because actualy,
- > we've got a huge amount of school work (X224 and X225 total rewrite,
- > final exams, reports for DecNet (250 pages), report for X224 ... :-((( )
-
- I'd say you've done a great job so far! X11R5 is running rather nicely
- on my PPI 33Mz Zeus system.
-
- Michael
-
- --
- Michael L. Hitch INTERNET: osymh@montana.edu
- Computer Consultant BITNET: OSYMH@MTSUNIX1.BITNET
- Office of Systems and Computing Services
- Montana State University Bozeman, MT USA
-
-