Re: Portable Allegroserve and SBCL

Petter Gustad <newsmailcomp6@xxxxxxxxxx> writes:

Ari Johnson <iamtheari@xxxxxxxxx> writes:

I'm trying to give Webactions from Portable Allegroserve 1.2.35 a
shot, and I got it to run on OpenMCL 1.0 with very few hassles (just
had to add some nicknames to acl-compat packages), but I would like
to be able to run it on SBCL. I happen to run Debian sarge on the

I haven't tried Portable Allegroserve/Webactions under SBCL, but I've
had it running (with CLSQL) under CMUCL for quite some time.

Probably the single hardest part of adjusting to CL for me has been
tracking down errors and bugs in large pieces of code that I did not
write. I would gladly fix every bug I found and send a patch to the
developer, but the problem is that I don't *find* bugs - I merely
*encounter* them. To actually find something implies a great deal
more specificity as to location than I seem to be able to accomplish.

Is there some easier way to track things down than:
- Looking for style warnings preceding the error to get clues
- Grepping through the possible files that may be involved to find
the symbols warned about
- Searching through the candidate file to find something related to
the error
- Scratching your head to figure out why the only candidate file
is one that the compiler said it successfully compiled
?

In C, you get a line number and file name to at least start your
search for the error from. Presumably there is some better way
available here, but so far the best I have been able to do is use a
backtrace to figure out whether it's a compiler error or a load error,
and which file is involved.
.

Relevant Pages

  • Re: .NET Umgebung mit MFC von Visual C 6 nutzbar?
    ... den Compiler vermisse ich in einigen Details ... Zu glauben das es irgendwo Bugs ... > Was hast Du für Probleme mit mit CFileDialog? ... Nachdem ich diese Fehler hatte bin ich dann kurzerhand wieder auf VS6 ...
    (microsoft.public.de.vc)
  • Re: compiler bugs
    ... well known verification techniques? ... think of the kind of bugs you experience. ... (Most compiler code is ... many of the subtle bugs come from using grey-areas, ...
    (comp.compilers)
  • Re: Perform Thru/Go to vs. Perform - Compile Speed
    ... >>and customers with such large programs must sometimes do what is ... a thing" is irrelevant when it comes to what a compiler encounters. ... the bugs being mentioned were "not an infrequent ... restictions -- it's difficult to support a rewrite just on accounta it looks ...
    (comp.lang.cobol)
  • Re: future C standards
    ... You asked me the reason for my "prejudice" against lcc-win, and that "disagreement" is a key part of it. ... surprising is that the bugs existed because of a failure to understand ... confidence in the quality of your compiler. ... so it would apply equally well to C90 as to C99. ...
    (comp.std.c)
  • Re: Whats more important optimisations or debugging?
    ... aiming to make high level debugging as accurate and complete as ... oriented debug chain is appropriate. ... But in either case, barring chip and compiler bugs, the bugs ...
    (comp.arch.embedded)