X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	chuckcar <chuck AT nil DOT car>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Re: 1] C compiler Flags 2]RHIDE Problem
Date:	Mon, 20 Nov 2006 03:04:03 +0100 (CET)
Organization:	Aioe.org NNTP Server
Lines:	82
Message-ID:	<Xns9880D7830B27Fchucknilcar@194.177.96.26>
References:	<0J8V009XK2Y0ZIC0 AT mta3 DOT srv DOT hcvlny DOT cv DOT net> <Xns987ECA9791717chuckcar AT 85 DOT 227 DOT 11 DOT 7> <0J8Y00L1VNPAGGA0 AT mta5 DOT srv DOT hcvlny DOT cv DOT net>
NNTP-Posting-Host:	uyQorf/ZYYN2NmoXJjzTmg.user.aioe.server.aioe.org
X-Complaints-To:	abuse AT aioe DOT org
User-Agent:	Xnews/5.04.25
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Ethan Rosenberg <ethros AT earthlink DOT net> wrote in
news:0J8Y00L1VNPAGGA0 AT mta5 DOT srv DOT hcvlny DOT cv DOT net: 

> At 07:47 PM 11/17/2006, you wrote:
>>Ethan Rosenberg <ethros AT earthlink DOT net> wrote in
>>news:0J8V009XK2Y0ZIC0 AT mta3 DOT srv DOT hcvlny DOT cv DOT net:
>>
>> > List members -
>> >
>> > Thank you for all your help.
>> >
>> > 1]  Where can I obtain a list of the C compiler and linker flags? 
>> > Is it obtainable from within DJGPP program?
>> >
>> > 2]  The problem in RHIDE only appears if I start RHIDE and press
>> > the ESC key when it loads, thereby forcing it to load the last open
>> > file.  If I explicitly request to load the file from the first
>> > dialog, the system is stable.  Can anyone explain this behavior?
>> >
>> > Much Thanks.
>> >
>> > Ethan Rosenberg
>> >
>> >
>>
>>I suggested earlier this week that you try rebuilding from sources.
>>Now another replier has as well and you don't reply to either of us.
>>Is there a common reason for this? Remember the answer that works
>>often isn't the answer you want to hear.
> 
> Chuck -
> 
> Thank you.
> 
> I am sorry that I did not reply sooner.  It is my last resort fall 
> back position.   I am not a programmer by training,  use C as a tool 
> for data reduction programs, and
> am worried that if I try a rebuild from source code, that I will 
> destroy everything.
> 
> I can probably duplicate the crash, but have not succeeded to get the 
> dump into a file.  If you would inform me how to send the dump to a 
> file, I can post that and obtain some guidance from the list as to 
> how to proceed.
> 
> Again, sorry for the tardiness of my reply.
> 
> Ethan
>>--
>>(setq (chuck nil)  car(chuck) )
> 
> 
> 

Sorry about the redirect - I reverted to msdog. it *should* be: 

rhide &> rhide.out

not rhide > rhide.out as previously posted.

note: that is *only* the normal output. for the actual dump you'll have
to run it under gdb: 

gdb rhide

:g
at this point it will run until it crashes. 

quit

will exit gdb.

you could redirect all output to a file as well, but then you wouldn't
see what it's putting out, so you wouldn't know when it's done so to
speak. copying from the bash window could also be done and the pasting
into a notepad would work. 

(s

-- 
etq (chuck nil)  car(chuck) )

- Raw text -