SIGABRT on version 3.0.15 #2079
Comments
|
The template for a new issue describes what information we need. Please follow the documentation. |
|
Hello, I'm sorry. I get next backtrace: Is it enough information about a crash? |
|
I'm sorry, have you any news about the problem? |
|
Your backtrace is content free. You didn't build with debugging symbols so there's no useful information. |
|
Okay. What about this trace: |
|
On Oct 25, 2017, at 5:20 AM, swood ***@***.***> wrote:
Okay. What about this trace:
Post the trace to github via the web site. If you use an HTML mailer, and paste the trace into the mail, it comes out unreadable.
i.e. look on github to see how useless that trace is.
|
|
I'm sorry, but what we are talking about: problem with software or about the decoration of message? |
|
On Oct 25, 2017, at 6:44 AM, swood ***@***.***> wrote:
I'm sorry, but what we are talking about: problem with software or about the decoration of message?
Go read the message on github, like I suggested. You will see what I'm talking about.
If the stacktrace is too hard for reading I will change it. But if it clear I think there is a more important question.
The only question right now is will you help fix the problem?
a) post unreadable stack traces and then argue about == no
b) do as I suggested == yes
|
|
I'm sorry, but I don't understand your wishes. Could you give me an example how to send to you readable stacktrace and will begin solve the problem with the FreeRadius? |
|
never mind... github was mangling the stack traces. The problem from the stack trace is that it's clear when the server is crashing. Just not why it's crashing. |
|
Do you mean request? I can't send to you full request log, but I can say that it was a simple authorization request via wi-fi. It was yesterday evening. If you need more information details please tell me. |
|
FR has stable working after upgrade to the last version 3.0.16.
2017-10-25 14:08 GMT+03:00 Alan DeKok <notifications@github.com>:
… never mind... github was mangling the stack traces.
The problem from the stack trace is that it's clear *when* the server is
crashing. Just not *why* it's crashing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2079 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIAQ_pjB1HYQAGR_a0r9412kmCmbXLkks5svxaxgaJpZM4Pk_vY>
.
--
Best regards,
Anton Kiryushkin
|
|
good, thanks, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello.
I have a strange fall down of the freeradius process version 3.0.15 (last stable version from your site). Do you need additional information about configuration or last auth request?
The text was updated successfully, but these errors were encountered: