Hi,
today I have found this. If You need more informations please let me know.
16:48:56 [WARN] {BUG} Bug: 0x1076f25 <_start+0xa5> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x1077119 <main+0x19> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x107727c <tor_main+0x4c> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x107bfe9 <tor_run_main+0xb9> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x107a221 <do_main_loop+0x411> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x801b4de1f <event_base_loop+0x51f> at /usr/local/lib/libevent-2.1.so.6 (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x801b51cd2 <event_base_assert_ok_nolock_+0xa92> at /usr/local/lib/libevent-2.1.so.6 (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x107fc3e <tor_run_main+0x3d0e> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x107e55b <tor_run_main+0x262b> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x11caf6a <tor_bug_occurred_+0x10a> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: 0x11aff98 <log_backtrace+0x48> at /usr/local/bin/tor (on Tor 0.3.4.9 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} Bug: Non-fatal assertion !(connection_is_reading(conn)) failed in conn_close_if_marked at src/or/main.c:1047. Stack trace: (on Tor 0.3.4.9 │ 4ac3ccf2863b86e7) │ 16:48:56 [WARN] {BUG} tor_bug_occurred_: Bug: src/or/main.c:1047: conn_close_if_marked: Non-fatal assertion !(connection_is_reading(conn)) failed. (on Tor 0.3.4.9 │ 4ac3ccf2863b86e7)
Cheers Dlugasny
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, November 28, 2018 5:02 AM, teor teor@riseup.net wrote:
Hi,
Thanks for reporting this bug.
On 28 Nov 2018, at 04:10, dlugasny@protonmail.com wrote: does any could tell me what is mean that Warn ? 16:32:33 [WARN] {BUG} Bug: 0x1076f25 <_start+0xa5> at /usr/local/bin/tor (on Tor 0.3.4.9 4ec3ccf2863b86e7) │ 16:32:33 [WARN] {BUG} Bug: 0x1077119 <main+0x19> at /usr/local/bin/tor (on Tor 0.3.4.9 4ec3ccf2863b86e7) │ 16:32:33 [WARN] {BUG} Bug: 0x107727c <tor_main+0x4c> at /usr/local/bin/tor (on Tor 0.3.4.9 4ec3ccf2863b86e7) │ 16:32:33 [WARN] {BUG} Bug: 0x107bfe9 <tor_run_main+0xb9> at /usr/local/bin/tor (on Tor 0.3.4.9 4ec3ccf2863b86e7) │ 16:32:33 [WARN] {BUG} Bug: 0x107a221 <do_main_loop+0x411> at /usr/local/bin/tor (on Tor 0.3.4.9 4ec3ccf2863b86e7) ─┘ 16:32:33 [WARN] {BUG} Bug: 0x801b4de1f <event_base_loop+0x51f> at /usr/local/lib/libevent-2.1.so.6 (on Tor 0.3.4.9 4ec3ccf2863b86e7)
Tor bugs come with a log message that tells us the assertion that failed. Is there any more log output around this bug?
I extracted that from Nyx. FreeBSD 11.1
We recently fixed a FreeBSD bug with a similar stacktrace. We're testing the fix in 0.3.5 before we backport it.
https://trac.torproject.org/projects/tor/ticket/27750
T