Project

General

Profile

Actions

Bug #2810

closed

Segfault in Wt::WMemoryResource::handleRequest

Added by Emeric Poupon about 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
03/13/2014
Due date:
% Done:

0%

Estimated time:

Description

(Upgrading from 3.3.1 to 3.3.2-rc2)

I use a WImage on a memoryresource.

The memoryresource is not set yet (empty)

When displaying the WImage, I get this

Program received signal SIGSEGV, Segmentation fault.

[Switching to Thread 0x7fffea1df700 (LWP 24786)]

Wt::WMemoryResource::handleRequest (this=0x7fffe4060c40, request=..., response=...) at /storage/emeric/MesProgs/wt/wt-3.3.2-rc2/src/Wt/WMemoryResource.C:112

112 for (unsigned int i = 0; i < (*data).size(); ++i)

(gdb) bt


Files

patch-empty-memoryresource (453 Bytes) patch-empty-memoryresource naive patch that fixes the problem Emeric Poupon, 03/13/2014 02:02 PM
Actions #1

Updated by Wim Dumon about 10 years ago

  • Status changed from New to Resolved

Thank you. I also made data() resistant to null data.

Actions #2

Updated by Koen Deforche about 10 years ago

  • Assignee set to Wim Dumon
  • Target version changed from 3.3.2 to 3.3.3
Actions #3

Updated by Emeric Poupon almost 10 years ago

Hey,

Is that "normal" that this bug is still in the git master branch?

Regards,

Emeric

Actions #4

Updated by Wim Dumon almost 10 years ago

Hi Emeric,

I noticed yesterday that I forgot to push that change. It's on its way now.

BR,

Wim.

Actions #5

Updated by Wim Dumon almost 10 years ago

But to answer your question: it should appear in a few days

Actions #6

Updated by Koen Deforche almost 10 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF