[Histogram] - Bug when removing image

Questions about Anatomist manipulation

Moderators: denghien, riviere

Post Reply
souedet
Posts: 15
Joined: Fri Sep 22, 2006 10:57 am

[Histogram] - Bug when removing image

Post by souedet »

Hello,

I open an image in an Histogram window. Then I remove the image from the main anatomist window (using CTRL+D keys) and anatomist closes with a segmentation fault.

The workstations I tried are is205629 (my own laptop), is204629 (workstation at NeuroSpin) and is122999 (workstation at NeuroSpin).
* On is205629 :
- OS is linux Mandriva-2008.0 system.
- account was ns215310.
- access was local.
- anatomist was stable repository version ( /i2bm/home/ns215310/Developments/p4/build-stable-Mandriva-2008.0-i686-debug/bin/anatomist ).
- config was i2bm_setup_repository.

* On is204629
- OS is linux Mandriva-2008.0 system.
- account was a-sac-ns-research.
- access was using ssh (ssh -l a-sac-ns-research is204629).
- anatomist was main repository version ( /home/a-sac-ns-research/build-main-Mandriva-2008.0-i686-release/bin/anatomist ).
- config was i2bm_setup_repository.

* On is122999
- OS is linux Fedora-4 system.
- account was a-sac-ns-research.
- access was using ssh (ssh -l a-sac-ns-research is204629).
- anatomist was main repository version ( ~/build-main-Fedora-4-i686-release/bin/anatomist ).
- config was i2bm_setup_repository.

I used the following image : /home/souedet/Petri/base/anso_sic_rat/1_rats_FDG_MG0701/rat_5_tests/autorad_last/tif/MG0701_rat5_auto_col0_sec16_test.ima but I tried with other images to and the same error occured.

Please see the attachment files.
Attachments
Screen before segmentation fault
Screen before segmentation fault
anatomist_histogram_1.png (123.44 KiB) Viewed 3388 times
Screen after segmentation fault
Screen after segmentation fault
anatomist_histogram_2.png (63.04 KiB) Viewed 3388 times
User avatar
riviere
Site Admin
Posts: 1361
Joined: Tue Jan 06, 2004 12:21 pm
Location: CEA NeuroSpin, Saint Aubin, France
Contact:

Re: [Histogram] - Bug when removing image

Post by riviere »

Hi Nicolas,
Right, it's fixed (we were not correctly using the Qwt5 API).
Denis
Post Reply