From: "Wesley W. Garland" <wes@page.ca>
To: overseers@sourceware.org
Cc: wes@page.ca
Subject: GDB Gnats is eating my submissions!
Date: Mon, 10 Sep 2007 17:53:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10709101351460.6495-100000@dent> (raw)
Hey, Guys!
(Thanks for the pointer, Daniel)
I'm trying to report a bug in GDB that inexplicably affects a LOT of my
code when building under gcc3.4 and Solaris 10 for gdb 6.x. (It's a
problem in dwarf2read.c and/or the format of the executable.. I don't know
enough about DWARF2 to comment more specifically).
Anyhow, I've tried twice now (once last week, once today) to submit this
bug, and it doesn't show up in gnats. I can't for the life of me figure
out why. I have filled out all the required fields, typed at length,
selected category symtab, not confidential, serious, medium, sw-bug. I
attached a 460K tar ball with a bunch of debug info and a sample
executable. I have not gotten any email about it, and I HAVE checked my
spam filter.
Can anybody help me out? I'd really like to file this bug, it has come up
before in the list, but the reporter never filed a bug nor sent along an
executable. I have a test case that is -- I believe -- 100% replicable on
my environment (GNU tool chain as shipped with Solaris 10 for SPARC
platforms), and triggered when the executable is first loaded (before
run).
Oh -- I'm not on this list. If you could CC me on replies, I'd appreciate
it.
Thanks,
Wes
--
Wesley W. Garland
Director, Product Development
PageMail, Inc.
+1 613 542 2787 x 102
next reply other threads:[~2007-09-10 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 17:53 Wesley W. Garland [this message]
2007-09-10 20:33 ` Jonathan Larmour
[not found] ` <be1f08ab0709101347p533a780x53779afee038a58c@mail.gmail.com>
2007-09-10 20:49 ` Wesley W. Garland
2007-09-10 21:07 ` Daniel Jacobowitz
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=Pine.GSO.4.10.10709101351460.6495-100000@dent \
--to=wes@page.ca \
--cc=overseers@sourceware.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: link
Be 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).