Any way to diagnose a package that is hurting an image?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Any way to diagnose a package that is hurting an image?

Rick Flower
I've got some old Seaside 2.8 code that is probably loading
something VW7.7 doesn't like but am not sure what.. I do
know that if I take a vanilla image, add Seaside (3.0) and
a few other contrib packages and then load my own code, I
frequently can't save the image afterwards.  I get a small
window up entitled "visual" with no content and VW just
hangs.. I've done this about 4-5 times this evening and
am a bit stumped.. Any suggestions?

Thanks in advance!
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: Any way to diagnose a package that is hurting an image?

Andres Valloud-6
It sounds familiar, although I had the problem starting up an image.  In
my case, I had a priority 100 process crash (e.g.: the process coming
back from a snapshot) in a way that stopped and also prevented the
debugger from coming up.  Since you're having the problem with saving an
image, I'd instrument UnhandledException>>defaultAction to write stack
dump to a file each time the method runs.  Thus, if the debugger becomes
necessary when an error is not handled, at least you know what's going
on even if the debugger fails to come up as a result of the problem.

Andres.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On
Behalf Of Rick Flower
Sent: Tuesday, May 25, 2010 12:07 AM
To: [hidden email]
Subject: [vwnc] Any way to diagnose a package that is hurting an image?

I've got some old Seaside 2.8 code that is probably loading something
VW7.7 doesn't like but am not sure what.. I do know that if I take a
vanilla image, add Seaside (3.0) and a few other contrib packages and
then load my own code, I frequently can't save the image afterwards.  I
get a small window up entitled "visual" with no content and VW just
hangs.. I've done this about 4-5 times this evening and am a bit
stumped.. Any suggestions?

Thanks in advance!
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: Any way to diagnose a package that is hurting an image?

Michael Lucas-Smith-2
In reply to this post by Rick Flower
On 5/25/10 12:07 AM, Rick Flower wrote:
> I've got some old Seaside 2.8 code that is probably loading
> something VW7.7 doesn't like but am not sure what.. I do
> know that if I take a vanilla image, add Seaside (3.0) and
> a few other contrib packages and then load my own code, I
> frequently can't save the image afterwards.  I get a small
> window up entitled "visual" with no content and VW just
> hangs.. I've done this about 4-5 times this evening and
> am a bit stumped.. Any suggestions?
>    
You can watch the list of prereqs that get loaded in the Transcript. Or
you could load the Seaside bundle from store and then anything "extra"
that gets loaded as a prereq -won't- be in the Seaside bundle.

Michael
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: Any way to diagnose a package that is hurting an image?

Holger Kleinsorgen-4
In reply to this post by Rick Flower
sounds like a borked subsystem, system event interest or dependent of
ObjectMemory.

Am 25.05.2010 09:07, schrieb Rick Flower:

> I've got some old Seaside 2.8 code that is probably loading
> something VW7.7 doesn't like but am not sure what.. I do
> know that if I take a vanilla image, add Seaside (3.0) and
> a few other contrib packages and then load my own code, I
> frequently can't save the image afterwards.  I get a small
> window up entitled "visual" with no content and VW just
> hangs.. I've done this about 4-5 times this evening and
> am a bit stumped.. Any suggestions?
>
>
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
J G
Reply | Threaded
Open this post in threaded view
|

Re: Any way to diagnose a package that is hurting an image?

J G
Holger,

A bit off topic but is sounds that you are not using Store?



On Tue, May 25, 2010 at 4:02 PM, Holger Kleinsorgen
<[hidden email]> wrote:

> sounds like a borked subsystem, system event interest or dependent of
> ObjectMemory.
>
> Am 25.05.2010 09:07, schrieb Rick Flower:
>> I've got some old Seaside 2.8 code that is probably loading
>> something VW7.7 doesn't like but am not sure what.. I do
>> know that if I take a vanilla image, add Seaside (3.0) and
>> a few other contrib packages and then load my own code, I
>> frequently can't save the image afterwards.  I get a small
>> window up entitled "visual" with no content and VW just
>> hangs.. I've done this about 4-5 times this evening and
>> am a bit stumped.. Any suggestions?
>>
>>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>



--
Best Regards,

Jim G

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc