Gtkmm-forge Digest, Vol 2, Issue 13



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 347857] The advanced printing example
      (gtkmm (bugzilla.gnome.org))
   2. [Bug 347857] The advanced printing example
      (gtkmm (bugzilla.gnome.org))
   3. [Bug 347857] The advanced printing example
      (gtkmm (bugzilla.gnome.org))


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

Message: 1
Date: Sat, 22 Jul 2006 09:46:23 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 347857] The advanced printing example
To: gtkmm-forge lists sourceforge net
Message-ID: <20060722094623 6E0F86C4126 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=347857
 gtkmm | general | Ver: 2.9.x





------- Comment #7 from Marko Anastasov  2006-07-22 09:46 UTC -------
I added the manual disconnecting when I noticed the segfault on program exit
and thought it's because ExampleWindow is destroyed before PrintFileOperations,
and I wanted the PFOs to be destroyed immediately after they're done and not on
program exit, so it's more like an experiment. It's something which rarely
needs to be done I know, but (only?) that way the program doesn't segfault on
exit after more than one PFO. But that does not affect the previewing stuff, it
has a much lower priority now so let's move on.

I get the same output in valgring, but I think it's missing a bit - see my gdb
backtrace in the first post (the segfault is in GTK's common_render_page()),
you should get the same. But that's just the diagnosis. When I would get a
segfault while writing the first test I'd see somewhere in GTK code that I
didn't create a cairo context for a print context or similar - something was
null, so I could tell. I don't know what that means here.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



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

Message: 2
Date: Sat, 22 Jul 2006 10:47:25 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 347857] The advanced printing example
To: gtkmm-forge lists sourceforge net
Message-ID: <20060722104725 B47B76C4146 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=347857
 gtkmm | general | Ver: 2.9.x





------- Comment #8 from Marko Anastasov  2006-07-22 10:47 UTC -------
I was comparing our priv object (GtkPrintOperationPrivate) that gets in
common_render_page() with the one in gtk+/tests/print-editor.c . The
difference:

- us: rloop = 0x0, start_page = 0, end_page = 0, end_run = 0
- them: rloop = 0x96b2400, start_page = 0xa9e1f0 <preview_start_page>, end_page
= 0xa9dff0 <preview_end_page>, end_run = 0xa9eea0 <preview_end_run>

For instance, preview_start_page() is at gtkprintoperation.c: 233 and it emits
got-page-size.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



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

Message: 3
Date: Sat, 22 Jul 2006 11:14:31 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 347857] The advanced printing example
To: gtkmm-forge lists sourceforge net
Message-ID: <20060722111431 059096C4147 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=347857
 gtkmm | general | Ver: 2.9.x





------- Comment #9 from Marko Anastasov  2006-07-22 11:14 UTC -------
Look in gtkprintoperation.c: print_pages() (line 2185): segfault occurs after
the preview signal is emitted of course (l. 2229), but before these callbacks
are set in the lines that follow.

The preview signal is not handled well, too much happens. In print-editor,
drawable's expose_event, where for us render_page() fails, is handled after
those callbacks are set. In our case, everything goes after preview is emitted,
but not everything is ready yet.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



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

-------------------------------------------------------------------------
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 2, Issue 13
******************************************



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]