From: David Edelsohn <dje@watson.ibm.com>
To: Chris Fury <cfury@bev.net>
Cc: egcs@cygnus.com
Subject: Re: egcs 1.1.1, AIX 4.1.5 and gdb...
Date: Mon, 14 Dec 1998 17:15:00 -0000 [thread overview]
Message-ID: <9812150115.AA32132@marc.watson.ibm.com> (raw)
In-Reply-To: <36757627.D0C86AF@bev.net>
>>>>> Chris Fury writes:
Chris> I have succesfully compiled egcs 1.1.1 with the --with-stabs option, but when
Chris> I try to use gdb to debug my program, it can't find the filenames. The
Chris> debugging
Chris> information seems to be using "short" filenames vs. long filenames with the
Chris> long paths. I need this functionality because I have many directories with
Chris> several files named the same thing in those directories.
Chris> Anybody out there seen this problem and/or know how to deal with it?
EGCS probably will not work on AIX using --with-stabs. There is
no special support in either the compiler or debugger to handle that.
Most of all, that configuration is not supported.
David
prev parent reply other threads:[~1998-12-14 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-14 12:26 Chris Fury
1998-12-14 12:43 ` Jeffrey A Law
1998-12-14 13:46 ` Chris Fury
1998-12-14 13:51 ` Jeffrey A Law
1998-12-14 17:15 ` David Edelsohn [this message]
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=9812150115.AA32132@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=cfury@bev.net \
--cc=egcs@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).