This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/3] bfd cache: tighten match criteria and debug commands.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Andrew Burgess <andrew dot burgess at embecosm dot com>
- Cc: palves at redhat dot com, gdb-patches at sourceware dot org
- Date: Wed, 15 Apr 2015 19:15:21 +0300
- Subject: Re: [PATCH 0/3] bfd cache: tighten match criteria and debug commands.
- Authentication-results: sourceware.org; auth=none
- References: <cover dot 1428941320 dot git dot andrew dot burgess at embecosm dot com> <552C326E dot 6080803 at redhat dot com> <20150415100954 dot GI2422 at embecosm dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Wed, 15 Apr 2015 11:09:54 +0100
> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Cc: gdb-patches@sourceware.org
>
> > The inode/dev info is available right there in the same fstat call
> > you are hooking into to retrieve the file size:
>
> <snip>
>
> > That "st" is a "struct stat", which contains:
> >
> > struct stat {
> > dev_t st_dev; /* ID of device containing file */
> > ino_t st_ino; /* inode number */
> > ...
> > off_t st_size; /* total size, in bytes */
> >
> > You'd just need to do the exact same you're already doing, but
> > store st_dev/st_ino instead of st_size? What am I missing?
>
> It's just my inability to communicate properly, my uncertainty only
> related to how I would implement a windows suitable solution, as was
> discussed in the thread I linked previously.
Windows can use an equivalent information, at least on NTFS.