thx for answer, i tried what you suggest but the problem persists. i also tried to compile python with -ggdb but that showed exactly the same stack as without the debug flags so i'm not sure what's wrong. i am noob wrt python and eclipse (i use netbeans) so i doubt i could manage to debug trac remotely within short time and i cannot afford to spend on it several hours or days.
miroslav Olemis Lang napsal(a): > 2009/9/15 Miroslav Šulc <[email protected]>: > >> hi, >> >> i have issues running some pages of trac, they simply do not load (empty >> page displays in browser). i found out in apache log that the cause is >> segmentation fault. here are the pages that cause seg fault: >> /browser >> /ticket/1 (any number) >> /changeset/349%3Afd2a05fbaab3 (any changeset) >> >> > [...] > >> i also tried to debug tracd but it seems i miss debug info in python and >> did not find a way how to turn it on: >> >> anyone has an idea why i get the segfaults and how to fix it? or at >> least how to turn on debugging symbols for python so i could see the >> cause in the stack? >> >> > > try this one : > > - Disable trac.versioncontrol.* > - Restart the server > > The only cause why I've experienced segfauls with Trac is > py-svn-bindings. If the problem persists at least you know that you > should look somewhere else ;o) > > Hint : You can debug Trac using PyDev + Eclipse ;o) > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
