public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: r.scher@varilog.com To: insight-gnats@sources.redhat.com Subject: insight/164: insight crashes on binaries from gpc (Gnu Pascal) 2.1 Date: Thu, 06 Jun 2002 11:23:00 -0000 [thread overview] Message-ID: <20020606181942.32091.qmail@sources.redhat.com> (raw) >Number: 164 >Category: insight >Synopsis: insight crashes on binaries from gpc (Gnu Pascal) 2.1 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Jun 06 11:23:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Robert Scher >Release: unknown-1.0 >Organization: >Environment: redhat 7.0, kernel 2.4.4 variant, glibc-2.1.92. >Description: I obtained sources to gpc version 2.1 at http://www.gnu-pascal.de/current/ namely, gpc-2.1 and gcc-core-2.95.2 I built & installed per instructions in p/INSTALL under the top-level source directory. I also built insight-5.2 from sources at your site. The insight that I built works fine on C programs. Programs large & small that I compile and link using gpc 2.1 have some slightly unusual stabs, perhaps. In any case, when I try to use insight to open such a file, insight crashes. This only happens in graphical mode, and I have tracked it down and can offer a prospective patch. insight works more or less normally on a gpc2.1 generated binary, except that all variables print as "void". This is a separate problem and looks to me like a gpc 2.1 defect. But this crash situation, I'm not sure who's not following the stabs spec., if there is such a thing... After getting your initial mail, I'll e-mail you three files: my patch (dbxread.c.diff) and the pascal source and gpc2.1-produced executable of "smalltest", a trivial program that will illustrate the crash. In particular a N_FUN with empty name appears at a point when When exercise insight in graphical found that insight (in graphical mode) crashes >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-06 18:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-06 11:23 r.scher [this message] 2002-06-11 10:53 Keith Seitz
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=20020606181942.32091.qmail@sources.redhat.com \ --to=r.scher@varilog.com \ --cc=insight-gnats@sources.redhat.com \ /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).