Project

General

Profile

Actions
Copy link

Bug #1425

closed

e.eventType() causes segfault if called after WApplication::notify(e)

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

Status:
Closed
Priority:
Normal
Assignee:
Michael Vilsker
Target version:
3.2.3
Start date:
09/06/2012
Due date:
% Done:

0%

Estimated time:

Description

Hello!

Here is a test-case.

Output:

...
[2012-Sep-06 14:44:33.025495] 29319 - [info] "WebRequest: took 1.305ms"
0
Segmentation fault

It is called by second e.eventType() (see event.bt)

PS. I can see errors like "DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction wi

th DW_OP_piece." in the backtrace. What do they mean?

Wt 3.2.1.

PS 2. There are too many bugs in last versions of Wt. Each next version is comming with fixes of bugs, but does introduce another bugs. My suggestion (inspired by Debian packages system) for you is to merge patches into old versions too. For example, when you release Wt 3.2.3, add all bug fixes to Wt 3.2.2 and call it Wt 3.2.2-2.

Files

Download all files
event.cpp (524 Bytes) event.cpp source Boris Nagaev, 09/06/2012 12:28 PM
event.bt (3.09 KB) event.bt backtrace Boris Nagaev, 09/06/2012 12:28 PM
Actions
Copy link
 #1

Updated by Koen Deforche about 12 years ago

  • Status changed from New to InProgress
  • Assignee set to Michael Vilsker
  • Target version set to 3.2.3

Hey,

We are planning to release 3.2.3 with a focus on bug resolution, while postponing a number of new features to 3.3.0. It is true that the past two releases have bitten us, but it is related to making a number of internal changes that were long due.

Regards,

koen

Actions
Copy link
 #2

Updated by Koen Deforche about 12 years ago

  • Status changed from InProgress to Closed
Actions
Copy link

Also available in: Atom PDF