www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2002/01/03/16:24:17

X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
Message-ID: <000d01c1949c$d798f820$1400a8c0@alex>
From: "Alex Oleynikov" <alex AT compuweigh DOT com>
To: <djgpp AT delorie DOT com>
Subject: Strange RHIDE behavior
Date: Thu, 3 Jan 2002 16:23:08 -0500
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Reply-To: djgpp AT delorie DOT com

Hello

Could somebody explain me the strange things that I found in RHIDE (or GCC)?

The story is: any function, which has an argument named "search_cond"
crashes when I try to step into it while debugging the application. The PC
screen just goes black with a blinking cursor and I have to reboot it again.
The strange thing is that stepping over the function works fine so does the
executable, when it is run from DOS prompt.
I tried all kinds of tricks to figure out where the problem hides, but only
renaming the argument in the function's definition from "search_cond" to
anything else helps the situation. I always used to think that compilers do
not care how the function's arguments are named as soon as they have correct
types, but apparently it is not so.

Is there a hidden or system variable in DJGPP that has the same name and
confuses the debugger?

Thanks,
Alex


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019