Re: [poedit-users] execution segmentation fault

Martin d'Anjou wrote:
> > will show before the crash. If not, then at least a gdb backtrace
> > would be useful. And of course, try 1.3.1 first, just in case.
>
> Ok. I think did all of that, except I use poedit 1.2.3. I used the
> debug flag and I got a gdb trace.

Sorry, but this is absolutely useless. First, forge about 1.2.3. 
Second, do you realize that backtraces from binaries *without 
debugging information* are of no value? From the look of it, it's not 
related to poEdit at all, it's more likely that you miscompiled 
something, but of course, the backtrace may be misleading if you 
produced it like this.

> USE="unicode gtk2 debug" emerge wxGTK poedit
>
> I put the whole thing on
> wget http://mda.zapto.org/files/mda/poedit.1.2.3.gdb.txt
> in order to keep the mailing list clean.
>
> The segmentation fault happens right after I click OK. 

First you claimed it crashes when you launch it, now it is after you 
click some OK button (which one? There are lots of them in the app.). 
Please make up your mind and provide *detailed* report as per the 
instructions on poedit.sf.net/support.php. If you can't describe the 
problem, I can hardly debug it.

Vaclav

-- 
PGP key: 0x465264C9, available from http://pgp.mit.edu/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQBBZnPjxDYa/UZSZMkRAntyAJ47uTuH8Mg2P+TbYLt/xnmnT3FLxQCeNopU
3sC+2vBr9nEn22tT38C3RmM=
=YP+B
-----END PGP SIGNATURE-----