public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/26106] [meta-bug] Gfortran can't compile tonto Date: Sat, 22 Apr 2006 04:48:00 -0000 [thread overview] Message-ID: <20060422044808.31338.qmail@sourceware.org> (raw) In-Reply-To: <bug-26106-682@http.gcc.gnu.org/bugzilla/> ------- Comment #21 from jvdelisle at gcc dot gnu dot org 2006-04-22 04:48 ------- I am able to compile with -g OK. Not sure what I was seeing the other night. Here is a backtrace where I see a segfault: (gdb) bt #0 0x082c1c15 in __atom_module__n_bf (self=@0xa2908a8) at f95files/atom.F90:2251 #1 0x082cb859 in __atomvec_module__n_bf (self=@0xa28fef8) at f95files/atomvec.F90:4147 #2 0x081296ae in __mol_module__set_basis_info (self=@0xa28fe28) at f95files/mol.F90:3473 #3 0x0812a519 in __mol_module__resolve_gaussianbasis_info (self=@0xa28fe28) at f95files/mol.F90:3355 #4 0x0812a5e0 in __mol_module__resolve_basis_info (self=@0xa28fe28) at f95files/mol.F90:3290 #5 0x080d5dd6 in __mol_module__read_atoms (self=@0xa28fe28) at f95files/mol.F90:9587 #6 0x0804e79d in __mol_main_module__process_keyword (self=@0x8513064, keyword=@0xbfaa5324, _keyword=128) at f95files/mol_main.F90:3844 #7 0x08050e13 in __mol_main_module__read_keywords (self=@0x8513064) at f95files/mol_main.F90:3815 #8 0x08051341 in __mol_main_module__main (self=@0x8513064) at f95files/mol_main.F90:3753 #9 0x08049a3c in MAIN__ () at f95files/run_mol.F90:134 #10 0x084a0ef7 in main (argc=Cannot access memory at address 0x3 ) at ../../../main/libgfortran/fmain.c:18 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26106
next prev parent reply other threads:[~2006-04-22 4:48 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-05 16:39 [Bug fortran/26106] New: " hjl at lucon dot org 2006-02-05 16:41 ` [Bug fortran/26106] [meta-bug] " pinskia at gcc dot gnu dot org 2006-02-05 17:37 ` pinskia at gcc dot gnu dot org 2006-03-11 19:27 ` kargl at gcc dot gnu dot org 2006-03-11 20:15 ` hjl at lucon dot org 2006-03-15 16:53 ` pault at gcc dot gnu dot org 2006-03-15 17:26 ` kargl at gcc dot gnu dot org 2006-03-15 19:31 ` hjl at lucon dot org 2006-03-15 20:02 ` kargl at gcc dot gnu dot org 2006-03-15 20:18 ` hjl at lucon dot org 2006-03-15 20:42 ` kargl at gcc dot gnu dot org 2006-03-15 23:28 ` hjl at lucon dot org 2006-03-15 23:33 ` Andrew Pinski 2006-03-15 23:33 ` pinskia at physics dot uc dot edu 2006-03-16 0:14 ` hjl at lucon dot org 2006-03-16 5:08 ` pinskia at gcc dot gnu dot org 2006-04-10 15:07 ` paul dot richard dot thomas at cea dot fr 2006-04-13 13:36 ` paul dot richard dot thomas at cea dot fr 2006-04-13 13:48 ` hjl at lucon dot org 2006-04-13 13:49 ` hjl at lucon dot org 2006-04-19 4:59 ` pault at gcc dot gnu dot org 2006-04-20 6:21 ` jvdelisle at gcc dot gnu dot org 2006-04-20 6:25 ` jvdelisle at gcc dot gnu dot org 2006-04-22 4:48 ` jvdelisle at gcc dot gnu dot org [this message] 2006-05-30 16:09 ` [Bug fortran/26106] [meta-bug] Gfortran can't compile tonto correctly hjl at lucon dot org 2006-07-30 23:27 ` hjl at lucon dot org 2006-08-10 12:11 ` paul dot richard dot thomas at cea dot fr 2006-08-10 16:40 ` hjl at lucon dot org
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=20060422044808.31338.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).