Error with SOS while debugging a method with more than 64 parameters

[missshaikh]

Rick Byers : Func-eval can fail while stopped in a non-optimized managed method that pushes more than 256 argument bytes

check the above URL i have same error

"Cannot evaluate expression because a thread is stopped at a point where garbage collection is impossible, possibly because the code is optimized."

how can i solve this???


if i extension C:\Windows\Microsoft.NET\Framework\v2.0.50727\sos. dll loaded
this on my VS immediate window
then its says

SOS not available while Managed only debugging. To load SOS, enable unmanaged debugging in your project properties.

Please help me out this.
i m very worried :'(

[Bassem]

Hello Missshaikh,

I think your problem is,
You are using sos.dll unmanaged library which you must set your solution properties to allow ummanaged code in debugging, do this:

from the solution explorer on left window or from view, RightClick on the solution icon -> Properties -> Debug
mark on "enable unmanaged code debugging" check box.
then Save.

I hope this will help you.
Regards,
Bassem

[missshaikh]

Thank you for reply,

i try to do this
solution icon -> Properties -> Debug
after this i can not find "enable unmanaged code debugging" check box.

i have this screen.
check my Image

[Bassem]

Hi Missshaikh,
You only clicked on the wrong icon.
Your solution has the name click2city, Right Click on it.
It's the second icon not the first one on top.

[Frinavale]

@missshaikh

When you get this error, are you "Debugging" the website or does it appear after you've published the website to a web server?

Have you tried publishing your site and seeing if it works there?

[missshaikh]

@Frinavale
yes this error come when i Debugging.not after the published .
:(

[missshaikh]

@Bassem

1st of all thanks for reply ..

the second icon is rebuild solution.and you said the click on Property.that is very last in Right Click on solution.
please can you give me snap shot for this?

[Bassem]

So sorry for this mistake !
I was talking about windows-forms application not web.
I'm sorry Missshaikh, I may confuse you.

Hoping my apology to be accepted,
Bassem

[Frinavale]

Yesterday I did a bit of research on your error and the best explanation that I found for what's going on is the debugger is having problems determining when it is appropriate to call the garbage collector while your DLL is running.

It doesn't appear to be anything wrong with your code but is rather a bug in the Visual Studio debugger.

I didn't find the answer to fixing this problem yesterday... I was hoping that Bassem had the answer.

Have you tried skipping over the error?
Or does the error stop the application completely?
Could you catch it and ignore it for now while you need to do debugging?

[missshaikh]

when this error comes my all other logic that based on that not runing.so it must to run . after the error it not stop my web application bcoz i catch this error.but try catch is not a rite solution i need a rite solution bcoz i need to run my all code.

Rick Byers : Func-eval can fail while stopped in a non-optimized managed method that pushes more than 256 argument bytes

check this link please and see this it is same as my error.

[Frinavale]

Does your code push more than 256 bytes of arguments onto the stack (are you passing large amounts of data between functions)?

Do you have a function that has 64 (or more) arguments?

What are you trying to debug?

Have you seen this article?

[missshaikh]

yes my functionis more then 64 arguments...
can you give me the URL or help for this?

i have a function that have more then 64 arguments.
can'nt i create the function more then 64 arguments???
why?

[Frinavale]

According to that article that you linked us to, you cannot have a method with more than 64 parameters because it pushes too much data onto the stack.

You need to re-think your function so that it uses less parameters.

Consider grouping the data into an Object and passing this data as a single Object instead of a whole bunch of individual values. When you pass ByVal, it pushes a copy of the item onto the stack, but when you pass an Object ByVal you are only passing a reference to the Object.

-Frinny