On Fri, 2009-07-24 at 09:15 -0400, John Dennis wrote: > On 07/24/2009 04:27 AM, George Chelidze wrote: > > On Fri, 2009-07-24 at 08:08 +0200, Alan DeKok wrote: > >> George Chelidze wrote: > >>> I didn't say it's an issue with freeradius. > >> If it's not a FreeRADIUS issue, then the question doesn't belong > on > >> the list. > > > > I have just realized that this question should have been posted to > > freeradius-devel list. Sorry for mistake. > > > >> You're asking us to support (for free) a module you wrote, > and/or an > >> OS that someone else wrote. > >> > >> Why? > > > > What kind of answer you would like to get? I am afraid I missed > > something while building freeradius the way I did so I asked what I > > asked. If I knew that I have built freeradius with enough parameters > to > > get the stack trace and I can't get it because I have some other OS > > related problem I would never asked this question on this list. I > still > > do not know it, so if someone can give me a hint, I'll be thankful. > > I have to agree with Alan, this is not a FreeRADIUS issue. It is > clearly > an OS and software development environment issue. You haven't even > stated what OS and architecture it is and your description of the > error is vague at best.
No, It's not a FreeRADIUS issue, it's an issue with my custom module. Let me say it again - I posted to the wrong list, sorry. > The man page for ptrace states it has architecture > specific limitations. You built a local copy using your own toolchain > and installed it in in a non-standard location, the ball is in your > court. My original question was about pstack not ptrace. If you mean pstack and "__pthread_threads_debug" stuff, I checked it before posting to this list. > Here is a hint which is appropriate for Linux. I assume the process is > aborting No, it's not, however your hists are useful. Thank you. Best Regards, George - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
