Corinna Vinschen wrote:
Searching the mailing list archives or looking into the FAQ would have
been of some help.
Rather than let this extremely unhelpful reply be the last word,
I'll relate my experience. I'm sorry, but it's nearly impossible
to do web searches on this topic. I know, I spen
Brian Ford wrote:
I've not done this in this way for cross debugging. What exact
functionality and licensing do you need here. Can gdb and binutils be
used?
No, that won't work for us. The code is part of a larger set of
tools to do, for example, execution tracing in a simulation
environmen
Dave Korn wrote:
What kind of UNIX ELF binaries? Have you tried binutils?
I'm not sure what you mean. Standard ELF executables with Dwarf
information. binutils won't work for me because this code is
integrated into larger tools that need the information.
-Dav
Hi all,
I've done some googling about libdwarf on cygwin and it seems
that at least one person has managed to compile libelf and
libdwarf for cygwin.
I'd like to use these libraries to examine executables produced
for non-Windows systems. That is, I need to create a tool to
examine the Dwarf fr
Brian Dessent wrote:
David Greene wrote:
Then please point me to them. My searches didn't turn up
anything.
http://www.google.com/search?q=site:cygwin.com+inurl:ml+inurl:cygwin+pthread+sigsegv+inurl:2006&num=100&filter=0
Thanks for the pointer. I installed the latest cygwin-
Eric Blake wrote:
Read the archives, this issue has already been beaten to death.
This is already fixed in CVS cygwin and CVS gdb; but until cygwin
1.5.20 is released, so that a new gdb snapshot can be provided,
you will have to use snapshots or resign yourself to hitting continue.
When is a n
Brian Dessent wrote:
David Greene wrote:
Program received signal SIGSEGV, Segmentation fault.
0x610af064 in pthread_mutex::init () from /usr/bin/cygwin1.dll
Please just consult the eleventy-billion previous threads on this
topic. Covered. To. Death.
Then please point me to them. My
David Greene wrote:
But my program also segfaults in pthread_mutex_init:
It turns out it also segfaults on pthread_mutex_lock
and pthread_mutex_unlock. Continuing works just fine.
But this is very annoying because the program doesn't
get very far before it has to do a lock or u
Apparently, the saga of pthreads and buggy gdb continues.
I've previously run into the famous gdb pthread_key_create
segfault on IRIX. Apparently it exists on Cygwin as well.
But my program also segfaults in pthread_mutex_init:
Program received signal SIGSEGV, Segmentation fault.
0x610af064 in
Richard Foulk wrote:
Those drive letters just get in the way. Don't use them.
But the whole point of my initial message is that I need
the drive letters because djgpp doesn't understand
network path names.
-Dave
--
Unsubscribe info: http://cygwin.com/ml/#unsubs
mwoehlke wrote:
Are you on a 64-bit Windows by any chance?
Nope.
If not, I won't be able to tell you why 'net' is being brain-dead, other
than "hmm, it does that sometimes; good luck!".
Well, I guess I'll just have to build locally then. That's
a real shame.
Larry Hall (Cygwin) wrote:
You mentioned that this is a share. Does anyone else have access to it?
If so, could they be making changes to these files?
No. This started happening when I was moved over to a Windows
XP PC. I can't be certain that Cygwin is the cause because I
immediately start
mwoehlke wrote:
You need to first do:
net use /delete h:
...so that you don't get prompted
Now I get this, which is what happened before I started
sshd as dag. Except I can still cd to //samba-drive/dag:
$ net use H: \\samba-drive\dag
System error 67 has occurred.
The network name cannot b
Larry Hall (Cygwin) wrote:
Windows apps like to set the execute bit on files. Have any of the
files you see this issue with been manipulated by Windows apps?
I don't think so. I've viewed directories in explorer. Would
that do it?
-Dave
--
Unsubscribe in
When I started using Cygwin to access files on a Samba-mounted
drive, I suddenly started seeing the UNIX permissions change
randomly. At one point, every file I owned on the network was
set to mode 700, regardless of whether I accessed the file or
the directory that contained it under Cygwin.
Th
mwoehlke wrote:
Anyway, the way I generally get things... well, closer to working, is to
create a service that calls 'bash -c ', and have
the script issue a bunch of 'net use ' commands and then exec
sshd. That way you don't have to worry about connections being
remembered, because they will
I know this subject has come up before but the most detailed
discussion I could find about the problem I'm having is here
http://erdelynet.com/archive/ssh-l/2002-12/0772.html
and this dates from Dec. 2002.
When I start a Cygwin xterm on the local machine, I can see
network drives just fine (these
17 matches
Mail list logo
