[Bug 1068967] New: internal cpp compiler error on Raspberry Pi 2
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967 Bug ID: 1068967 Summary: internal cpp compiler error on Raspberry Pi 2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: bnc-team-screening@forge.provo.novell.com Reporter: freek@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 749380 --> http://bugzilla.opensuse.org/attachment.cgi?id=749380&action=edit Source file which gives compile error When using the command: g++ -Wall -O2 -DUSE_SQLITE -c CSVexport.cpp -o obj/Release_SQLite/CSVexport.o I got the following message: CSVexport.cpp: In function ‘char* FormatFloat(char*, float, int, int, char)’: CSVexport.cpp:56:7: internal compiler error: Illegal instruction char *FormatFloat(char *str, float value, int width, int precision, char decimalpoint) ^~~~~~~~~~~ Please submit a full bug report, with preprocessed source if appropriate. I will attach the source code. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967
Freek de Kruijf
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967#c1
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967#c9
--- Comment #9 from Andreas Färber
(In reply to Richard Biener from comment #2)
More interesting information is a gdb session that shows the illegal instruction and where (in what binary/library) it happens.
Please provide the gdb command I should use.
gdb --args g++ ...
run
would probably be a good start? Having the debug symbol packages installed for any libraries it warns about on gdb start may be helpful. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967#c14
--- Comment #14 from Freek de Kruijf
(In reply to Freek de Kruijf from comment #3)
Please provide the gdb command I should use.
gdb --args g++ ...
run
would probably be a good start? Having the debug symbol packages installed for any libraries it warns about on gdb start may be helpful.
Used this command and added repository http://download.opensuse.org/ports/armv7hl/debug/tumbleweed/repo/oss/ Installed three infodebug packages. Running the above command did not show any more information. Please advice what I can do! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967#c17
--- Comment #17 from Andreas Färber
(In reply to Andreas Färber from comment #9)
(In reply to Freek de Kruijf from comment #3)
Please provide the gdb command I should use.
gdb --args g++ ...
run
would probably be a good start? Having the debug symbol packages installed for any libraries it warns about on gdb start may be helpful.
Used this command and added repository http://download.opensuse.org/ports/armv7hl/debug/tumbleweed/repo/oss/ Installed three infodebug packages. Running the above command did not show any more information.
Please advice what I can do!
This comment was submitted before the core discussions and ran into a mid-air collision - just for information for how to use gdb next time. bt (backtrace) would be the standard command to check for once gdb recognizes the crash. But as Andreas pointed out that it's actually cc1plus crashing it may be more difficult. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967
http://bugzilla.opensuse.org/show_bug.cgi?id=1068967#c21
--- Comment #21 from Freek de Kruijf
participants (1)
-
bugzilla_noreply＠novell.com