public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@redhat.com>
To: berek@usa.net
Cc: sourcenav@sourceware.cygnus.com
Subject: RE: replace (plain text)
Date: Wed, 04 Jul 2001 15:11:00 -0000	[thread overview]
Message-ID: <994284670.1236.1.camel@ghostwheel.cygnus.com> (raw)
In-Reply-To: <NFBBLPGOFICNAFDHEABHOEEOCDAA.berek@usa.net>

> most trivial of code bases. You call this "whining" [smile]? And, BTW, it's
> not one bug. it's many.
> 

That's the problem.  We don't know if it one or more without a good
testcase...

> I just sent a small part of my latest code base to a cohort of yours in the
> UK. I included screen captures of a couple of bugs, including (MS Visual
> Studio) memory, registers, error messages, disassembly at the location of
> the error (access violation in dbimp) and all of the source code he needed
> to reproduce and solve the problem. His response was that it was too much
> info for him to download and that he was reluctant to receive source code
> that didn't belong to me (it belongs to my employers). He then asked me if I
> could provide him with an "example" of the source code that caused the
> problem [AAAAARRRRRGGGGGHHHHH!!!!!]. Is there something wrong with this or
> is it me?

It is just you, of course, being that cohort I can't comment for anyone
else ;)  Without the code being released by your company via a written
release I can't look at it.  The best example is, of course, what you
sent me.  However, without a release from your company no one at Red Hat
can look at it.  If you can perhaps come up with a contrived example
that evokes the same behavior it would be wonderful.  As far as it being
too big, I work on the compiler most of the time - testcases are usually
small :)

-eric

-- 
I will not grease the monkey bars

  reply	other threads:[~2001-07-04 15:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29  7:02 replace Aurelian Melinte
2001-07-03 13:12 ` replace Mo DeJong
2001-07-03 13:54   ` replace Gacquer William
2001-07-03 14:45     ` replace Mo DeJong
2001-07-03 15:32       ` SN +gvim + ex-ctags == excellent free IDE Subrata Datta
2001-07-03 18:37       ` replace (plain text) Berek Half-hand
2001-07-03 22:54         ` Eric Christopher
2001-07-04 11:49         ` Mo DeJong
2001-07-04 12:09           ` Berek Half-hand
2001-07-04 15:11             ` Eric Christopher [this message]
2001-07-09  7:17               ` Aurelian Melinte
2001-07-04 13:52           ` Gacquer William
2001-07-04 14:38             ` Mo DeJong
2001-07-04 15:10               ` Gacquer William
2001-07-05 18:21                 ` Mo DeJong
2001-07-06 13:41           ` Andrew Cagney

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=994284670.1236.1.camel@ghostwheel.cygnus.com \
    --to=echristo@redhat.com \
    --cc=berek@usa.net \
    --cc=sourcenav@sourceware.cygnus.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: 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).