--- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-31
04:16 ---
I cannot reproduce this and this works for everyone else.
--
What|Removed |Added
--- Additional Comments From mark at klomp dot org 2005-01-27 22:44 ---
Subject: Re: gij exits with SIGABR
Could you try running it under gdb and show the backtrace when it
aborts.
$ gdb gij
> run Test
{... Abort ...}
> bt
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19586
--- Additional Comments From rickard dot narstrom at gmail dot com
2005-01-27 22:29 ---
hmmm I don't think this is a normal behavor, shulden't it use english in all
this cases
% echo $LANG
sv_SE.UTF-8
% LANG=C gij Test
Avbruten (SIGABRT)
% env LANG=C gij Test
Avbruten (SIGABRT)
% ex
--- Additional Comments From rickard dot narstrom at gmail dot com
2005-01-27 22:18 ---
(In reply to comment #8)
> Subject: Re: gij exits with SIGABR
>
> Do you hav some locale set?
> Try running your program with LANG=C.
>
>
Dosen't help att all, I only get the "aborted" message in
--- Additional Comments From mark at klomp dot org 2005-01-27 20:56 ---
Subject: Re: gij exits with SIGABR
Do you hav some locale set?
Try running your program with LANG=C.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19586
--- Additional Comments From rickard dot narstrom at gmail dot com
2005-01-27 17:36 ---
Memtest86+ passed all tests without any error... So the error is elsewere
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19586
--- Additional Comments From rmathew at gcc dot gnu dot org 2005-01-27
12:48 ---
> > Now it sounds like your machine has bad memory. Can you check your memory?
>
> I don't think so it probebly some bad updated env-vars that were back to
> correct
> values after a re-login or something
--- Additional Comments From rickard dot narstrom at gmail dot com
2005-01-23 20:15 ---
(In reply to comment #4)
> (In reply to comment #3)
> > the segfault seemed to be a tempurary failure its back to abort now
>
> Now it sounds like your machine has bad memory. Can you check your mem
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-23
19:54 ---
(In reply to comment #3)
> the segfault seemed to be a tempurary failure its back to abort now
Now it sounds like your machine has bad memory. Can you check your memory?
--
http://gcc.gnu.org/bugzilla/
--- Additional Comments From rickard dot narstrom at gmail dot com
2005-01-23 19:52 ---
the segfault seemed to be a tempurary failure its back to abort now
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19586
--- Additional Comments From rickard dot narstrom at gmail dot com
2005-01-23 17:59 ---
# gcj -v
Reading specs from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/specs
Configured with: /var/tmp/portage/gcc-3.4.3.20050110/work/gcc-3.4.3/configure
--enable-version-specific-runtime-libs --prefix=/
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-23
15:50 ---
This works for everyone I know about. Could you give more information than
what is here and what is
in the gentoo bug. Like how gcc was configured/built (this was on bugs.html if
the gentoo people
poin
12 matches
Mail list logo
