What to include when creating a distribution using cygwin?
Fri Jul 16 07:56:00 GMT 1999
Earnie Boyd <email@example.com> writes:
> > To simulate this, I copied these four files into the same directory as the
> > executable, and ran it. Unfortunately this causes "invalid page fault in
> > module <unknown> at 0000:cc267bb8. Running it under gdb is slightly more
> > illuminating - I include the output with backtrace below. It all seems to
> > fall over in something called from cygwin_crt0 somewhere.
> > What am I missing?
> Firstly, you can't have more than one copy of the cygwin dll in the
> executable path. Multiple instances of the dll can cause this problem.
Ah - OK. I've experimented with this however (setting 'export PATH=.' for
example), and still had the same problem. :(.
> Secondly, I wouldn't be distributing the kernel32.dll as it could lead
> you down the road to a law suit. Besides, every win32 system comes with
> it's own kernel32.dll as it is the core of Win32.
Thanks - actually I only copied three of the files into the directory, not
kernel32 as I guessed as much.
> Is there some reason to still be with the b19 distribution? It is a bit old
> now and a lot of bugs fixed and new enhancements with b20 and b21 is looming
> around the corner.
I used the B19 initially because I was initially replicating the work of a
colleague who used this version. I've upgraded to B20 and tried that
today. Unfortunately this causes more problems.
I now get a SIGSEGV somewhere in my code when it runs (actually in a
"schedule_parents_of" function). However, gdb seems unable to tell me where
in the function it failed, and is also unable to single step into the
function, displaying the source lines. I don't understand this as all the
code has been compiled (and linked) with -g. The gdb output is included
below - both the change and schedule_parents_of functions are from my code,
but the reference back to the source code is missing.
Under B19 I was able to compile and run, and had problems with packaging
the thing for use on other peoples PCs without the full cygwin
environment. Now under B20 (with the same source code) it will not run, and
debugging is made hard by this problem with gdb.
Thanks for the help - does anybody know 1) which files to include and where
to put them in a package for distributing software using cygwin, Tcl and Tk
to a more "virgin" PC? or 2) what might be causing gdb to loose debugging
symbols in some parts of gcc-compiled software?
Gdb output follows: -------------------------------------------------------
BASH.EXE-2.02$ gdb --nw tkeden.exe
GNU gdb 4.17.1
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-cygwin32"...
Starting program: /Ash/PhD/Tkeden/pctkeden/tkeden.exe
[failed reading symbols from DLL]
"/WINDOWS/SYSTEM/COMDLG32.DLL": error reading line numbers
DoNaLD init file is - /Ash/PhD/Tkeden/lib/tkeden/donald.init.e.
Program received signal SIGSEGV, Segmentation fault.
0x414202 in schedule_parents_of ()
#0 0x414202 in schedule_parents_of ()
#1 0x41440d in change ()
#2 0x412341 in assign () at machine.c:876
#3 0x403ab0 in execute (p=0x443370) at code.c:131
#4 0x401b09 in run (type=1, ptr=0x2740974,
name=0x42681c "/lib/tkeden/donald.init.e") at main.c:576
#5 0x426967 in init_donald () at dd_lex.c:842
#6 0x401df1 in main (argc=1, argv=0x2740ad8) at main.c:710
#7 0x61004402 in _size_of_stack_reserve__ ()
#8 0x61004420 in _size_of_stack_reserve__ ()
#9 0x436dfa in cygwin_crt0 (f=0x401d34 <main>)
Gdb output ends: -------------------------------------------------------
Ashley Ward - Graduate Teaching Assistant - PhD year 1
firstname.lastname@example.org - http://www.dcs.warwick.ac.uk/~ashley/
Room 102, Department of Computer Science, University of Warwick, Coventry
Want to unsubscribe from this list?
Send a message to email@example.com
More information about the Cygwin