From: "Kris Warkentin" <kewarken@qnx.com>
To: "Kris Warkentin" <kewarken@qnx.com>,
"Daniel Jacobowitz" <drow@mvista.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: Interesting dwarf-2/shared lib problem.
Date: Tue, 02 Dec 2003 17:11:00 -0000 [thread overview]
Message-ID: <028801c3b8f7$837f0b40$0202040a@catdog> (raw)
In-Reply-To: <025701c3b8f4$6e1cfb70$0202040a@catdog>
> Ah...interesting. For the main object, the symtab points to
> c:\some_dir\main.c and the symtab->next points to just main.c. It's the
> main.c that gets caught and returned. In the solib, we only see the
> c:\some_lib\display.c so the FILENAME_CMP fails..
>
> So you are correct, lookup_partial_symtab is failing.
Looks like lbasename() in libiberty/lbasename.c is failing. The
IS_DIR_SEPARATOR macro isn't being defined for __CYGWIN__ so when we've
compiled something with dos style paths...you get the picture. I fixed it
in our source but someone might want to ponder this....
Index: lbasename.c
===================================================================
RCS file: /product/tools/gdb/libiberty/lbasename.c,v
retrieving revision 1.2
diff -u -r1.2 lbasename.c
--- lbasename.c 6 Sep 2002 20:21:02 -0000 1.2
+++ lbasename.c 2 Dec 2003 17:10:58 -0000
@@ -46,7 +46,7 @@
#endif
#if defined (_WIN32) || defined (__MSDOS__) \
- || defined (__DJGPP__) || defined (__OS2__)
+ || defined (__DJGPP__) || defined (__OS2__) || defined (__CYGWIN__)
# define HAVE_DOS_BASED_FILE_SYSTEM
# ifndef DIR_SEPARATOR_2
# define DIR_SEPARATOR_2 '\\'
cheers,
Kris
next prev parent reply other threads:[~2003-12-02 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 16:12 Kris Warkentin
2003-12-02 16:18 ` Daniel Jacobowitz
2003-12-02 16:49 ` Kris Warkentin
2003-12-02 17:11 ` Kris Warkentin [this message]
2003-12-02 17:17 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='028801c3b8f7$837f0b40$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox