After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 163992 - segfault with Widget::get_default_colormap()
segfault with Widget::get_default_colormap()
Status: RESOLVED INVALID
Product: gtkmm
Classification: Bindings
Component: general
2.4
Other Linux
: Normal normal
: ---
Assigned To: gtkmm-forge
gtkmm-forge
: 164006 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-01-13 21:06 UTC by Marco Scholten
Modified: 2005-01-17 08:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
compilable test case (601 bytes, application/octet-stream)
2005-01-14 20:55 UTC, Marco Scholten 		Details

Description Marco Scholten 2005-01-13 21:06:32 UTC 
Create a window with one button
then do

  for (int i = 0 ; i<1000;++i)
  {  std::cout << i << std::endl;
     Glib::RefPtr<Gdk::Colormap> colormap = Button.get_default_colormap ();
  }

it will count to 4 and then segfault
Comment 1 Olav Vitters 2005-01-13 23:12:55 UTC 
*** Bug 164006 has been marked as a duplicate of this bug. ***
Comment 2 Murray Cumming 2005-01-14 07:30:02 UTC 
I can not reproduce this. What version of gtkmm are you using? If you are using
a latest stable or unstable version then please submit an actual compileable
test case.
Comment 3 Marco Scholten 2005-01-14 20:55:58 UTC 
Created attachment 36032 [details]
compilable test case

I'm using gtkmm 2.4.8
On debian unstable.
Comment 4 Marco Scholten 2005-01-16 16:44:23 UTC 
Little mistake here, i didn't have 2.4.8 installed but 2.4.7.
And after upgrading to 2.4.8 the problem was gone, so i guess this bug can be 
closed.
Comment 5 Murray Cumming 2005-01-17 08:32:25 UTC 
Thanks.