https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #14 from Aleks ---
Created attachment 223541
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223541&action=edit
core2
--
You are receiving this mail because:
You are on the CC list for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254303
--- Comment #15 from Aleks ---
(In reply to Alexander V. Chernikov from comment #13)
Apart from main trace and the one I've sent you yesterday?
I've attached another one (named core2) to this bugreport
--
You are receiving this mail becau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254478
Andrey V. Elsukov changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254478
--- Comment #2 from Andrey V. Elsukov ---
Created attachment 223546
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=223546&action=edit
proposed patch (untested)
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254478
--- Comment #3 from Daniel Kempkens ---
(In reply to Andrey V. Elsukov from comment #1)
> I think such problem can be reproduced if you will do open/close divert
> socket in a loop. Is it possible that your application sometimes does that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254478
--- Comment #4 from Andrey V. Elsukov ---
(In reply to Daniel Kempkens from comment #3)
inp_flags2 = 16
it looks like my guess was correct, PCB has INP_FREED flag set, so its socket
is already closed and should not be used. Proposed patch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254507
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254514
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
