Send Gtkmm-forge mailing list submissions to
        [EMAIL PROTECTED]

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
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

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 372642] on_*() methods are not called for    wrapped
      objects (gtkmm (bugzilla.gnome.org))
   2. [Bug 372642] on_*() methods are not called for    wrapped
      objects (gtkmm (bugzilla.gnome.org))
   3. [Bug 362181] Cairo::RefPtr leaking memory
      (gtkmm (bugzilla.gnome.org))
   4. [Bug 362181] Cairo::RefPtr leaking memory
      (gtkmm (bugzilla.gnome.org))
   5. [Bug 362181] Cairo::RefPtr leaking memory
      (gtkmm (bugzilla.gnome.org))
   6. [Bug 375009] Crash while inside a signal handler
      (gtkmm (bugzilla.gnome.org))
   7. [Bug 378810] New: Extra signals documentation not used
      (glibmm (bugzilla.gnome.org))
   8. [Bug 378524] Gtk::UIManager crashes when  exceptions are
      disabled (gtkmm (bugzilla.gnome.org))


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

Message: 1
Date: Thu, 23 Nov 2006 21:40:57 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 372642] on_*() methods are not called
        for     wrapped objects
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
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=372642

  gtkmm | general | Ver: 2.4.x





------- Comment #7 from Murray Cumming  2006-11-23 21:39 UTC -------
> You may be surprised, but it will just crash without "useless" call

Ah, I didn't see that you were registering your own wrap_new() rather than
re-registering the existing wrap_new(), and depending on that somehow.

This is a massive hack that has never been intended to be supported. You
shouldn't be messing about with these internals of gtkmm or GTK+. But that's a
discussion for your bug #373110, I think.


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



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

Message: 2
Date: Thu, 23 Nov 2006 23:42:32 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 372642] on_*() methods are not called
        for     wrapped objects
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
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=372642

  gtkmm | general | Ver: 2.4.x





------- Comment #8 from Paul Pogonyshev  2006-11-23 23:41 UTC -------
Then inheritance of gtkmm classes is yet more restricted in usage.  Granted,
you can inherit widgets and instantiate your own using constructors, but if
registering wrappers is not supported, it cannot be used for GTK+-created
widgets at all...  Why restrict users of the library?  Do you expect this
machinery to change or is there another good reason?


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



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

Message: 3
Date: Fri, 24 Nov 2006 09:22:49 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 362181] Cairo::RefPtr leaking memory
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
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=362181

  gtkmm | general | Ver: 2.10.x





------- Comment #4 from [EMAIL PROTECTED]  2006-11-24 09:21 UTC -------
Created an attachment (id=77091)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=77091&action=view)
Compilable test case

compile with:
g++ -o cairo-test `pkg-config --libs --cflags gtkmm-2.4` `pkg-config --libs
--cflags cairomm-1.0` main.cc


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



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

Message: 4
Date: Fri, 24 Nov 2006 09:24:40 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 362181] Cairo::RefPtr leaking memory
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
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=362181

  gtkmm | general | Ver: 2.10.x





------- Comment #5 from [EMAIL PROTECTED]  2006-11-24 09:23 UTC -------
So here it is. Happy Thanksgiving!

A run of valgrind for 30 seconds or so gives this 'definitely lost' report:

==16024== 204,048 (12,816 direct, 191,232 indirect) bytes in 267 blocks are
definitely lost in loss record 121 of 123
==16024==    at 0x40053C0: malloc (vg_replace_malloc.c:149)
==16024==    by 0x4066AC8: cairo_create (in /usr/lib/libcairo.so.2.10.0)
==16024==    by 0x4B2513: gdk_cairo_create (in
/usr/lib/libgdk-x11-2.0.so.0.1000.6)
==16024==    by 0xA5494D: Gdk::Drawable::create_cairo_context() (in
/usr/lib/libgdkmm-2.4.so.1.0.30)
==16024==    by 0x804CA47: CairoTest::on_expose_event(_GdkEventExpose*)
(main.cc:28)
==16024==    by 0x2257942:
Gtk::Widget_Class::expose_event_callback(_GtkWidget*, _GdkEventExpose*) (in
/usr/lib/libgtkmm-2.4.so.1.0.30)
==16024==    by 0x7130FF: (within /usr/lib/libgtk-x11-2.0.so.0.1000.6)
==16024==    by 0x2F8578: (within /lib/libgobject-2.0.so.0.1200.4)
==16024==    by 0x2F9D8A: g_closure_invoke (in /lib/libgobject-2.0.so.0.1200.4)
==16024==    by 0x30B352: (within /lib/libgobject-2.0.so.0.1200.4)
==16024==    by 0x30BFC6: g_signal_emit_valist (in
/lib/libgobject-2.0.so.0.1200.4)
==16024==    by 0x30C3B8: g_signal_emit (in /lib/libgobject-2.0.so.0.1200.4)


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



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

Message: 5
Date: Fri, 24 Nov 2006 09:26:25 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 362181] Cairo::RefPtr leaking memory
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
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=362181

  gtkmm | general | Ver: 2.10.x





------- Comment #6 from [EMAIL PROTECTED]  2006-11-24 09:24 UTC -------
Created an attachment (id=77092)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=77092&action=view)
valgrind output snippet

Bah, it mangled the last one...


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



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

Message: 6
Date: Fri, 24 Nov 2006 10:17:04 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 375009] Crash while inside a signal
        handler
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
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





------- Comment #3 from Alexis Wilke  2006-11-24 10:15 UTC -------
I registered bug 378779 in link with the G_OS_WIN32 and G_PLATFORM_WIN32
#define's which don't make it to the /mingw/include/glib folder.

That could be it... but I still need to recompile everything so it may take
another day or two to get an answer. If any structure changes depending on
these flags, then that's a very bad one.


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



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

Message: 7
Date: Fri, 24 Nov 2006 12:45:48 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
        <[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 378810] New: Extra signals
        documentation not       used
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]/>
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=378810

  glibmm | documentation | Ver: unspecified

           Summary: Extra signals documentation not used
           Product: glibmm
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: documentation
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]
         QAContact: [EMAIL PROTECTED]
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Since we made gmmproc automatically add a Doxygen comment block with the signal
handler's signature, Doxygen no longer uses any comment block that we added
manually. We get, for instance:

 /** The delete_event signal is emitted if a user requests that
  * a toplevel window is closed. The default handler for this signal
  * hides the window.
  *
  * @param event the event which triggered this signal.
  * @result true to stop other handlers from being invoked for the event, 
  * or false to propagate the event. further.
  */

/** @par Prototype:
   * <tt>bool %delete_event(GdkEventAny* event)</tt>
   */

  Glib::SignalProxy1< bool,GdkEventAny* > signal_delete_event();


Unless they are all in one /** * **/ block, only the second set of text is
used.


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



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

Message: 8
Date: Fri, 24 Nov 2006 19:19:50 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
        <[EMAIL PROTECTED]>
Subject: [gtkmm bugzilla] [Bug 378524] Gtk::UIManager crashes when
        exceptions are disabled
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
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=378524

  gtkmm | general | Ver: unspecified


Johannes Schmid changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #77064|none                        |committed
               Flag|                            |
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED




------- Comment #3 from Johannes Schmid  2006-11-24 19:18 UTC -------
Committed to gtkmm-2-6, gtkmm-2-8 and HEAD!


-- 
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
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest, Vol 6, Issue 19
******************************************
_______________________________________________
gtkmm-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gtkmm-list

Reply via email to