Bugzilla – Full Text Bug Listing |
Summary: | recursive algorithm problematic in nix routing | ||
---|---|---|---|
Product: | ns-3 | Reporter: | Mathieu Lacage <mathieu.lacage> |
Component: | routing | Assignee: | Josh Pelkey <joshpelkey> |
Status: | NEW --- | ||
Severity: | normal | CC: | joshpelkey, ns-bugs, riley, tomh |
Priority: | P5 | ||
Version: | pre-release | ||
Hardware: | All | ||
OS: | All |
Description
Mathieu Lacage
2010-04-12 05:28:52 EDT
Are you suggesting that the recursion is a problem in general and should be changed? Or are you reporting a bug using your example program and pointing out that it's problematic to debug given the amount of recursion. In other words, is this a memory issue, or a new undetermined problem when using nix-vector in a certain scenario? (In reply to comment #1) > Are you suggesting that the recursion is a problem in general and should be > changed? Or are you reporting a bug using your example program and pointing The recursion is a problem in this case: my source -> destination path is 255 hops (max ip path size) and the stack size is around 32K which does not appear to be sufficient beyond 200-something hops. So, I have tried to increase the stack size and it does fix the problem but my (dumb user) perspective is that it would be nice if the nix vector support did not use stacks that big. |