zed
Stack overflow, but can't change the code
My issue is that I have a calculation that overflows the stack by a little bit (it's deterministic and will never increase past around 1.15 MB). I can't change the code to not do that, unless business approves some funds for serious refactoring, so the question is, how to proceed. I wanted to increase the stack size to 2MB for the one calculation thread, which seems pretty reasonable. But not sure what the best way to do that would be.
Starting a new thread with the specified amount will mean I have to do some extra exception processing. How would I do that? Try/catch around the thread's code, and hoist the exception object out of the stack? Then rethrow from the outside? I will lose internal stack information that way, no? Throw a new exception on the outside, with the exception object as the inner exception? A bit more annoying to handle, but could work... are there any better ideas?
This isn't a normal "thread" scenario, since I start the thread and immediately join it, I don't actually want anything to run in parallel, I only do it to increase the stack size. So does this give me other options? Runtime cost of spawning/joining a new thread in this scenario is irrelevant.
Alternatively, is there a better way to handle the stack size increase?
5 replies
✅ Modify embedded resources at runtime
Is there a way to modify an assembly's own embedded resources? I'm not looking into physically changing the file, but (ideally) just virtually change what it produces, when an embedded resource is requested.
The context here being that I'm interfacing with a third party component which reads data only from an embedded resource, but I want to feed it data that is generated at runtime - it has no other way (that I know of) to interface with my project, other than through reading of embedded resources.
While the "third" party component is technically developed in-house, it's from a closed off development team, and they said they have no resources to devote to changing this behavior. So I'm not sure what else I could do.
Unfortunately, this is .NET Framework 4.8, so I don't have some newer features available to me.
Any ideas?
9 replies
✅ Resolving an ambiguous assembly reference
We recently upgraded an included NuGet package from version
2.0.1 to 3.0.1 (Spring.NET, in case it matters). Now we get this exception:
This indicates, that we missed upgrading one of our components, but we cannot find out which one. We're also including some third party components, which have (ostensibly) also been updated to use Spring.NET 3.0.1. But the provider assures us, that all projects in their solution were upgraded to use version 3.0.1. Now we're at a loss.
Is there a way to get more detailed information on which of our assemblies or components tries to reference the older version? A plain text search across all our .csproj and .config files revealed no reference to 2.0.1, and we're not sure what else to do.50 replies