On 30 August 2006 21:54, Danny Smith wrote:
> Dave Korn
>>
>> On 30 August 2006 16:19, Pierre Baillargeon wrote:
>>
>>> I've identified the reason why DLL don't show up: in the startup code
>>> (winsup/cygwin/dcrt0.cc), in dll_crt0_0(), Win32's SetErrorMode() is
>>> called to suppress all OS err
Dave Korn
>
> On 30 August 2006 16:19, Pierre Baillargeon wrote:
>
> > I've identified the reason why DLL don't show up: in the
> startup code
> > (winsup/cygwin/dcrt0.cc), in dll_crt0_0(), Win32's
> SetErrorMode() is
> > called to suppress all OS error dialogs. It's there since 1998
> > ac
On 30 August 2006 16:19, Pierre Baillargeon wrote:
> I've identified the reason why DLL don't show up: in the startup code
> (winsup/cygwin/dcrt0.cc), in dll_crt0_0(), Win32's SetErrorMode() is
> called to suppress all OS error dialogs. It's there since 1998 according
> to the changelog, so it mus
I've identified the reason why DLL don't show up: in the startup code
(winsup/cygwin/dcrt0.cc), in dll_crt0_0(), Win32's SetErrorMode() is
called to suppress all OS error dialogs. It's there since 1998 according
to the changelog, so it must not bother many people... I guess it would
be ugly to
Shankar Unni wrote:
Pierre Baillargeon wrote:
Thanks for the information. I will not submit a patch because I
suspect the current behavior is prefered by the majority: having a
dialog pop-up in the middle of scripts is much more catastrophic is
most case than having a return code, for unatten
Pierre Baillargeon wrote:
Thanks for the information. I will not submit a patch because I suspect
the current behavior is prefered by the majority: having a dialog pop-up
in the middle of scripts is much more catastrophic is most case than
having a return code, for unattended processing. So I
Thanks for the information. I will not submit a patch because I suspect
the current behavior is prefered by the majority: having a dialog pop-up
in the middle of scripts is much more catastrophic is most case than
having a return code, for unattended processing. So I expect the patch
to be bad
Now, the analysis: according to strace, the spawning process (e.g., the
shell) does receive the Windows exception C135 (a.k.a.
STATUS_DLL_NOT_FOUND), handles it, and uses it to set exit code to 0x35.
My guess is that neither cmd.exe nor the Windows launcher install a
handler for the exception
On Thu, 24 Aug 2006, Pierre Baillargeon wrote:
> Ok, first I want to show you the minimal test-case I built. Using Visual
> Studio 8, I created a solution containing two projects: a Win32 console
> application and a Win32 DLL. I deleted all the generated stuff and
> replaced them with a single fil
mwoehlke wrote:
What I expected is a dialog would pop-up saying "XYZ.dll not found"
like cmd.exe does, for example.
I assume you are running 'on the glass'?
I just verified the same behavior (no error popup, non-zero exit status)
'on the glass' - tcsh and bash in a native windows command w
Ok, first I want to show you the minimal test-case I built. Using Visual
Studio 8, I created a solution containing two projects: a Win32 console
application and a Win32 DLL. I deleted all the generated stuff and
replaced them with a single file per project.
The console application project is c
On Thu, 24 Aug 2006, Pierre Baillargeon wrote:
> Igor Peshansky wrote:
>
> > You really haven't given us enough to go on here. What is the
> > program, which DLL is it missing, how do you know it requires it, etc,
> > etc.
>
> I know, because it's a program I wrote. It's a DLL loaded by the Windo
Igor Peshansky wrote:
> One thing in your setup is that you have both Cygwin and MKS in your path,
> and that's just asking for trouble. But I doubt it's the cause of your
> current problem.
True enough, I can try uninstalling it now that I use cygwin exclusively, but
I concur that it is probably
Pierre Baillargeon wrote:
Problem: when running a program from bash and the program requires a DLL
that is missing (or lacks a particular function), I do not get any error
message nor dialog box. Only a exit status of 128. Can I change this
behavior?
What I expected is a dialog would pop-up s
On Wed, 23 Aug 2006, Pierre Baillargeon wrote:
> Hi,
>
> Problem: when running a program from bash and the program requires a DLL
> that is missing (or lacks a particular function), I do not get any error
> message nor dialog box. Only a exit status of 128. Can I change this
> behavior?
>
> What I
15 matches
Mail list logo
