Project

General

Profile

Actions
Copy link

Bug #1509

open

possible segfault in Wt

Added by Boris Nagaev about 11 years ago. Updated about 11 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
11/04/2012
Due date:
% Done:

0%

Estimated time:

Description

Hello!

I found non-reproducible segfault in my application. But I have a backtrace. Possible reason is Wt.

Wt version: b50f9b97f49054abb0fe3 (near 3.2.1)

Boost 1.42

Files

bt (3.28 KB) bt Backtrace Boris Nagaev, 11/04/2012 06:43 PM
Actions
Copy link
 #1

Updated by Koen Deforche about 11 years ago

  • Status changed from New to Feedback

Hey,

I couldn't find a fault: the accept() logic is pretty much taken from a boost asio example. It could ofcourse be that the reason is a problem elsewhere in Wt, in a totally unrelated place. On the other hand, we haven't seen any such issue with the publicly deployed (and high traffic) homepage and examples...

If it does happen again, it would be good to be able to valgrind it (or build using google's recently announced "compile-time valgrind").

Regards,

koen

Actions
Copy link

Also available in: Atom PDF