public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Berek" <berek@usa.net>
To: "Story, Lenny" <LStory@AstralPoint.com>,
	"Mo DeJong" <mdejong@cygnus.com>,
	<sourcenav@sourceware.cygnus.com>
Subject: Re: Windows NT Failing on XRef Generation.
Date: Fri, 09 Feb 2001 09:57:00 -0000	[thread overview]
Message-ID: <009201c092c1$bd9f6fe0$3e6410ac@concord.com> (raw)
In-Reply-To: <8F1BE54DECC1D211BB2500105A9CA42101C1C878@admin1.astralpoint>

I share your frustration with Red Hat. I bought the Enterprise Edition of SN
just before it went "Open Source" (I'm now using 4.5.2). The C++ xref is
virtually useless; many basic functions do not work (try using the "Context"
and "Reuse" boxes); history traversal is spotty with single windows and a
nightmare (unusable) with split windows; the Win/NT GUI has more holes in it
than a pound of Swiss cheese...the list is endless. When you talk to the Red
Hat folks about these defects, the response is always "Fix it yourself or
pay us to do it for you". Syd Polk tells us that C++ parser and xref bugs
are a high priority with Red Hat, but when asked about Release 5.0,
apparently most, if not all, of the work has been spent reworking the GUI.
As I write this, dbimp just croaked on an invalid memory reference while
doing some sort of background processing. Bottom line is that the idea of SN
is wonderful and such a product is long overdue, but the implementation is
disgraceful. My $0.02 worth.

----- Original Message -----
From: "Story, Lenny" <LStory@AstralPoint.com>
To: "Mo DeJong" <mdejong@cygnus.com>; <sourcenav@sourceware.cygnus.com>
Sent: Friday, February 09, 2001 11:32
Subject: RE: Windows NT Failing on XRef Generation.


> Hmm,
>
> Ok...so ...your saying that the problem doesn't
> exist...and you are unwilling to do anything about
> it unless i can point you directly to the issue...?
>
> If i could do that i would fix it myself.
>
> is this the kind of service we can expect if we purchase
> the product...(and service contract) from you ?
>
> The FACT is that it does BREAK. and a core dump is more than
> enought information to find the issue. Many people have
> encountered this problem, and are frustrated by it.
>
> This is exactly why FREE software is NOT the way to go...
> free obviously means that if it breaks your DEAD IN THE WATER....
> therefore companies cannot put any trust in them.
>
>
> -Lenny
>
>
> -----Original Message-----
> From: Mo DeJong [ mailto:mdejong@cygnus.com ]
> Sent: Thursday, February 08, 2001 11:29 PM
> To: sourcenav@sourceware.cygnus.com
> Subject: RE: Windows NT Failing on XRef Generation.
>
>
> On Thu, 8 Feb 2001, Story, Lenny wrote:
>
> > Well,
> >
> > I can reproduce it 100% of the time on my code base....
> > i've attached the Dr.Watson log entry for it....it should
> > help you determine what is happening....I HOPE you keep the
> > map..and list files....it will be your only way to corrolate
> > the minimal assembly dump with the code...
>
> When we say "can you reproduce the problem", the correct
> answer is not "yes" :) We need you to create a small
> one file example that will crash the parser. Trim
> your code down to a very small file that still
> crashes and then post it to the list. We are not
> going to go rummaging around in your core dumps,
> you need to provide a small example that
> demonstrates the problem.
>
> Mo DeJong
> Red Hat Inc
>
>

  reply	other threads:[~2001-02-09  9:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09  8:36 Story, Lenny
2001-02-09  9:57 ` Berek [this message]
2001-02-09 10:45   ` Kenneth Luke
2001-02-09 12:01 ` Mo DeJong
2001-02-09 12:27   ` Timothy M. Shead
  -- strict thread matches above, loose matches on Subject: below --
2001-02-09 18:29 Story, Lenny
2001-02-09 11:41 Story, Lenny
2001-02-08 20:16 Story, Lenny
2001-02-08 20:29 ` Mo DeJong
2001-02-08 20:16 Story, Lenny
2001-02-08 16:15 Story, Lenny
2001-02-08 12:14 Story, Lenny
2001-02-08 12:25 ` Ian Roxborough
2001-02-08  9:52 dave.banham
2001-02-08  9:05 Story, Lenny
2001-02-08  9:55 ` Syd Polk
2001-02-08 11:25 ` Berek

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='009201c092c1$bd9f6fe0$3e6410ac@concord.com' \
    --to=berek@usa.net \
    --cc=LStory@AstralPoint.com \
    --cc=mdejong@cygnus.com \
    --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).