From: Richard Dawe <rich@phekda.freeserve.co.uk>
To: gdb@sources.redhat.com,
Richard Dawe <rich@phekda.freeserve.co.uk>,
Eli Zaretskii <eliz@is.elta.co.il>
Subject: Re: gdb 5.3 (& earlier): Crash with mixed debug formats
Date: Tue, 24 Dec 2002 04:18:00 -0000 [thread overview]
Message-ID: <3E085023.415DB634@phekda.freeserve.co.uk> (raw)
In-Reply-To: <3E083C24.63AF6C93@phekda.freeserve.co.uk>
Hello.
Richard Dawe wrote:
> I discovered recently that the DJGPP port of gdb crashes, when you have a
> mix stabs+ and DWARF-2 debug information and try to tab-complete a function
> name.
[snip]
Andris Pavenis, one of the DJGPP developers, reported just now in a message
entitled "GDB-5.3 for DJGPP" on the djgpp-workers mailing list (see
http://www.delorie.com/djgpp/mail-archives/ ) that:
"I had one problem with using GDB-5.3 prereleases built for DJGPP. The reason
is errorous line info generated by gcc (at least 3.1, 3.2, 3.2.1), when
command line option -imacros is being used (we use it from specs to get
sys/version.h included automatically).
The result from that is GDB internal error. I don't currently have time to dig
into that too much, so only thing I have done is to patch one of sources in
GDB to workaround this problem (I have only seen while loading information
about preprocessor macros it when -gdwarf-23 or -g3 is used).
I'm now in Latvia for Christmass and New Year holydays and don't have this
patch anywhere near me now. I can only send it after I'll return in Finland in
January"
I wonder if anyone can reproduce the problem using my example modified to use
-imacros and, say, gcc 3.2.x on Linux.
Thanks, regards,
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
prev parent reply other threads:[~2002-12-24 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 2:54 Richard Dawe
2002-12-24 4:18 ` Richard Dawe [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=3E085023.415DB634@phekda.freeserve.co.uk \
--to=rich@phekda.freeserve.co.uk \
--cc=eliz@is.elta.co.il \
--cc=gdb@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: 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