Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [aspectj-users] LTW: Problem generating method, Code size too big

Hi Ron,

Thanks for your reply. Is there any quick work-around
for now? I am happy if I can somehow access the
original un-weaved class and replace the the invalid
class when I encounter this error.

 
--- Ron Bodkin <rbodkin@xxxxxxxxxxxxxx> wrote:

> It seems to me that the right thing to do would be
> to create a private
> method and include some of the excessive sized code
> in that method. I am
> guessing that that's a small project and not a quick
> fix.
> 
> This might be a great one for an interested
> contributor... it would be great
> if this summer AspectJ recruited contributors for
> Google's Summer of Code
> program.
> 
> -----Original Message-----
> From: aspectj-users-bounces@xxxxxxxxxxx
> [mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf
> Of Eric Bodden
> Sent: Thursday, March 08, 2007 8:32 PM
> To: aspectj-users@xxxxxxxxxxx
> Subject: Re: [aspectj-users] LTW: Problem generating
> method, Code size too
> big
> 
> Werll, I guess that's a technical limitation of the
> bytecode weaving
> approach. Java methods have a size restriction of
> 64K. If your method
> is really large and has a lot of joinpoint shadows
> it might sometimes
> go above this limit during weaving. IMHO giving you
> the error message
> you are seeing now is a reasonable thing to do. I am
> not sure if it
> would be good to just not weave the class in that
> case. I rather
> prefer error messages when something goes wrong. But
> this might depend
> on the application, I guess...
> 
> Eric
> 
> On 08/03/07, jennie <jenniemai81@xxxxxxxxx> wrote:
> > Hi there,
> >
> > Has anyone gotten a similar error?
> >
> > problem generating method
> > org.apache.jsp.main_jsp._jspService : Code size
> too
> > big: 70282
> >
> > When I tried to decompile with jad, jad also
> > complained that it couldn't fully decompile
> > _jspService. The class after weaving seems to be
> > corrupted. I'm wondering if the correct behavior
> > should be to leave the "too big" class alone after
> > encountering this error?
> >
> > I added a comment to this bug that seems related:
> >
> >
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=138384
> >
> > Thanks for the help.
> >
> >
> >
> >
>
____________________________________________________________________________
> ________
> > Don't pick lemons.
> > See all the new 2007 cars at Yahoo! Autos.
> > http://autos.yahoo.com/new_cars.html
> > _______________________________________________
> > aspectj-users mailing list
> > aspectj-users@xxxxxxxxxxx
> >
>
https://dev.eclipse.org/mailman/listinfo/aspectj-users
> >
> 
> 
> -- 
> Eric Bodden
> Sable Research Group
> McGill University, Montréal, Canada
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/aspectj-users
> 
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/aspectj-users
> 



 
____________________________________________________________________________________
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121


Back to the top