From: "Jesús Guerrero" <i92guboj@terra.es>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] FVWM taskbar segfault on ~amd64
Date: Fri, 29 Feb 2008 15:55:41 +0100 [thread overview]
Message-ID: <20080229155541.4d687b67.i92guboj@terra.es> (raw)
In-Reply-To: <20080229064829.GA28460@crowfix.com>
On Thu, 28 Feb 2008 22:48:29 -0800
felix@crowfix.com wrote:
> On Thu, Feb 28, 2008 at 07:57:42PM +0100, Jes?s Guerrero wrote:
>
> > Gentoo doesn't add too much stuff. Just a couple of patches. But it
> > would help if you can reproduce your problem with a vanilla build of
> > fvwm. Without patches. So we can confirm that it's an fvwm problem.
>
> > With my fvwm cvs ebuild you can do this, to get a vanilla build:
> >
> > USE="-extras -translucency" emerge =fvwm-9999
First, lets see if the new vanilla build gives you the same problem. In
that case you can compile with USE="debug" to get a debug build of fvwm.
>
> OK, it's compiling right now. All I have for an error is the segfault
> line in syslog. Should I run fvwm with any particular args to get a
> core dump or anything useful? I am also willing to try special
> builds, but you'd have to hold my hand for whatever gentoo tricks that
> would require. Or running it under gdb, I could probably do that, but
> I am not sure how one would go about that since it is a window manager.
Look here, particularly sections df1 and df3.
http://www.starshine.org/xteddy/thomas/fvwm/fvwmchanfaq.html#df1
If we can reproduce the same error with the vanilla build, then the
backtrace would belong to the fvwm-workers@fvwm.org mailing list, where
the fvwm can give you a better advice and the bug would probably be hunted
and tracked much more faster than I could do.
--
Jesús Guerrero <i92guboj@terra.es>
--
gentoo-amd64@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-02-29 14:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 5:24 [gentoo-amd64] FVWM taskbar segfault on ~amd64 felix
2008-02-21 5:41 ` Jesús Guerrero
2008-02-21 16:26 ` felix
2008-02-21 18:44 ` Jesús Guerrero
2008-02-21 19:04 ` felix
2008-02-21 19:42 ` Jesús Guerrero
2008-02-21 21:08 ` Sebastian Redl
2008-02-21 21:47 ` felix
2008-02-21 21:54 ` felix
2008-02-21 22:40 ` Jesús Guerrero
2008-02-21 23:00 ` felix
2008-02-28 8:33 ` felix
2008-02-28 18:57 ` Jesús Guerrero
2008-02-29 6:48 ` felix
2008-02-29 14:55 ` Jesús Guerrero [this message]
2008-02-29 17:03 ` felix
2008-03-01 1:55 ` [gentoo-amd64] " Duncan
2008-03-01 15:33 ` felix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080229155541.4d687b67.i92guboj@terra.es \
--to=i92guboj@terra.es \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox