Bug #2810
closedSegfault in Wt::WMemoryResource::handleRequest
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
Updated by Wim Dumon almost 11 years ago
- Status changed from New to Resolved
Thank you. I also made data() resistant to null data.
Updated by Koen Deforche almost 11 years ago
- Assignee set to Wim Dumon
- Target version changed from 3.3.2 to 3.3.3
Updated by Emeric Poupon over 10 years ago
Hey,
Is that "normal" that this bug is still in the git master branch?
Regards,
Emeric
Updated by Wim Dumon over 10 years ago
Hi Emeric,
I noticed yesterday that I forgot to push that change. It's on its way now.
BR,
Wim.
Updated by Wim Dumon over 10 years ago
But to answer your question: it should appear in a few days
Updated by Koen Deforche over 10 years ago
- Status changed from Resolved to Closed