public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andris Pavenis <andris@latnet.lv>
To: "Raúl Duque" <rduque@andromeda.uanarino.edu.co>, gcc-help@gcc.gnu.org
Subject: Re: compiling problem DJGPP
Date: Wed, 10 Apr 2002 00:33:00 -0000	[thread overview]
Message-ID: <200204100729.01620.andris@latnet.lv> (raw)
In-Reply-To: <5.1.0.14.0.20020409100423.0319e5e0@andromeda.uanarino.edu.co>

Viestissä Tiistai 9. Huhtikuuta 2002 15:14, Raúl Duque kirjoitti:
> Hello.
>
> I had a old djgpp distribution and worked well. About a month a downloaded
> a new distribution with GCC 3.03 and RHIDE 1.4.9 (I download RHIDE 1.4.9.1
> too) but the debuging system is failing. For example I add a breakpoint and
> the debug say "No code generated for this line" but it's false. When I can
> debug step to step the actual line isn't selected, several times the
> debuging system crash.
> I think it's a RHIDE problem but I cann't fix it. Any suggestons?
>

This message is off topic in GCC related mailing list. Use DJGPP mailing list
(djgpp@delorie.com) or RHIDE mailing list (rhide-users@lists.sourceforge.net)

You may try my later build of RHIDE available from
	http://www.rhide.com/snapshots
however the debugging support with gcc-3.0.X seems to work worse for DJGPP as 
with earlier versions. The debugging support is from GDB, so how good will be 
it there, so it will be in RHIDE. 

Andris

  reply	other threads:[~2002-04-10  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09  9:21 Raúl Duque
2002-04-10  0:33 ` Andris Pavenis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-11 10:38 Raúl Duque
2001-12-13 11:16 ` Andris Pavenis

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=200204100729.01620.andris@latnet.lv \
    --to=andris@latnet.lv \
    --cc=gcc-help@gcc.gnu.org \
    --cc=rduque@andromeda.uanarino.edu.co \
    /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).