GNOME.org
 

Gtkmm-forge Digest, Vol 6, Issue 12

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-owner lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 374094] Freeing Gtk owned memory in
      Gtk::Style::lookup_icon_set (gtkmm (bugzilla.gnome.org))
   2. [Bug 375009] New: Crash while inside a signal	handler
      (gtkmm (bugzilla.gnome.org))
   3. [Bug 375009] Crash while inside a signal handler
      (gtkmm (bugzilla.gnome.org))


----------------------------------------------------------------------

Message: 1
Date: Tue, 14 Nov 2006 03:18:51 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 374094] Freeing Gtk owned memory in
	Gtk::Style::lookup_icon_set
To: gtkmm-forge lists sourceforge net
Message-ID: <20061114031851 3C9E36C40AD box gnome org>
Content-Type: text/plain; charset=utf-8

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=374094

  gtkmm | general | Ver: unspecified


Nate Nielsen changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|gtkmm-                      |nielsen memberwebs com
                   |forge lists sourceforge net |




------- Comment #4 from Nate Nielsen  2006-11-14 03:17 UTC -------
IconSet has neither reference() nor operator bool().  Should those methods be
added?


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email



------------------------------

Message: 2
Date: Tue, 14 Nov 2006 07:16:04 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 375009] New: Crash while inside a
	signal	handler
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-375009-5595 http bugzilla gnome org/>
Content-Type: text/plain; charset=utf-8

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=375009

  gtkmm | general | Ver: 2.10.x

           Summary: Crash while inside a signal handler
           Product: gtkmm
           Version: 2.10.x
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: general
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: alexis m2osw com
         QAContact: gtkmm-forge lists sourceforge net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Steps to reproduce:
We are creating a proprietary application, so we cannot just copy the code
here. However, the application works just fine under Linux, it crashes under 
Win32 in a timeout callback (our auto-save feature uses a sigc++ signal to
receive a callback whenever our timer times out).

This is the setup call and the callback function we use:

...

  Glib::signal_timeout().connect( sigc::mem_fun(*this, &MainWindow::OnTimer),
SAVE_TIMEOUT_SECS * 1000 );

...

bool MainWindow::OnTimer()
{
        Save();
        return true;
}

Our main problem is that we needed 2.8 before a pre-compiled version was
available and now we need 2.10 before a pre-compiled version is available...

Using the pre-compiled versions has worked (well, it has worked great with
2.8).

I tried to call the Save() by itself under Win32, and the file got saved just
fine. So I cannot blame the Save() function itself, and since we can run the
App for hours under Linux, there does not seem to be any good reason for this
crash other than some incompatible compile (i.e. a structure/object size
mismatched between two libraries).

Stack trace:
This varies. So one stack trace would not give you much.

The problem is with memory allocation and as you know where it crashes is just
the next new/delete/free/malloc which happen to stumble on the bad memory
chunk.

Yet, this only seems to happen in our timeout handler. The rest of our
application works just fine.

Other information:
What I can share, no problem, is the source of all the pre-compiled binaries
and the source that I have to compile to get everything up to date.

This is what I compile:

        cairomm-1.2.2
        libsigc++-2.0.17
        glibmm-2.12.2
        gtkmm-2.10.2

Everything compiles just fine after I fixed the gtkmm configure script (see bug
#371882).

Otherwise, I use the following packages:

  atk-1.12.3.zip
  atk-dev-1.12.3.zip
  cairo-1.2.6.zip
  cairo-dev-1.2.6.zip
  glib-2.12.4.zip
  gtk+-2.10.6.zip
  gtk+-dev-2.10.6.zip
  pango-1.14.5.zip
  pango-dev-1.14.5.zip

These come from different ftp sites.

  ftp://ftp.gnome.org/pub/GNOME/binaries/win32/
  ftp://ftp.gtk.org/pub/gtk/v2.10/win32/

And when available, the mm files are here:

  http://www.pcpm.ucl.ac.be/~gustin/win32_ports/

but at this time I didn't see the gtkmm 2.10.x suite.

Since some people may ask, we tested the code on Celeron's, Pentium 4's and
AMD's. Under Linux: fine; under Win32: crash. So I'm sure the problem is some
memory management, possibly from some incompatibilities between the different
libraries (i.e. glib compiled with different structures than glibmm...)

What I'm after is mainly an insight to search where the bug is. I'll be glad to
squish it for you otherwise.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email



------------------------------

Message: 3
Date: Tue, 14 Nov 2006 17:01:52 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 375009] Crash while inside a signal
	handler
To: gtkmm-forge lists sourceforge net
Message-ID: <20061114170152 E81F16C410A box gnome org>
Content-Type: text/plain; charset=utf-8

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=375009

  gtkmm | general | Ver: 2.10.x


R. Douglas Barbieri changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |doug dooglio net




------- Comment #1 from R. Douglas Barbieri  2006-11-14 17:00 UTC -------
Could this be because the Glib::signal_timeout() is emitting from a different
thread under Win32 but not Linux? This bug smacks of a multi-thread problem.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email



------------------------------

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

------------------------------

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest, Vol 6, Issue 12
******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]