Ticket #977 (closed enhancement: fixed)

Opened 2 years ago

Last modified 2 years ago

There is no applicable method for the generic function: CCL::%%ONE-ARG-DCODE

Reported by: fare Owned by:
Priority: normal Milestone:
Component: Compiler Version: trunk
Keywords: Cc:

Description

At times, our application QRes has the following error message:

There is no applicable method for the generic function:

<Compiled-function CCL::%%ONE-ARG-DCODE #x3000002039CF>

when called with arguments:

(NIL)

The backtrace subsequently reveals that there was an actual bug in our application relating to a calling a one-argument generic function with an invalid value. However, the name of said generic function was lost in this error message.

Can CCL somehow improve its error message by revealing the name of the user function that got optimized into a CCL::%%ONE-ARG-DCODE ?

Xref: ITA bug 113986 Xref: ITA bug 105855

Change History

comment:1 Changed 2 years ago by gb

r15279 fixed a known case of this in 1.8.

It seems likely that either:

  1. you're not running 1.8
  2. you're seeing an unknown case

If (1), I don't know whether or not we've committed to supporting old versions for your company, but in general we don't have the resources to do that.

If (2), we would have to know something about the case that you're seeing.

The case that r15279 addresses involves generic functions whose methods are all reader-methods; when certain optimizations were performed, the optimized code didn't need access to the generic function for method dispatch (and stored something else where the generic function would ordinarily be found), but reporting a NO-APPLICABLE-METHOD error accessed that "something else" instead of the GF.

I'm not aware of any other cases where something like this happens in CCL itself, but your application likely contains CLOS optimization code that we no longer have access to and we have no way of knowing what that code does.

comment:2 Changed 2 years ago by fare

The bugs were indeed reported before we upgraded to 1.8.

I don't believe we have seen it since. I will reopen the bug if that happens.

My apologies for being slow at reporting all the bugs from our bugzilla to your trac.

I believe there are no pending bugs anymore, this was the last one.

Thanks a lot for your support.

comment:3 Changed 2 years ago by fare

  • Status changed from new to closed
  • Resolution set to fixed

Marking as fixed.

Note: See TracTickets for help on using tickets.