Ah, typically, it's not always optimized out everywhere. The trick is to
find a frame where you still have access to the structure and get the fd
value. For instance in frame 6:
#6 0x0000003407a094ca in XrdFfsWcache_create (fd=0) at
/usr/src/debug/xrootd/xrootd/src/XrdFfs/XrdFfsWcache.cc:114
we know fd is zero and in that frame we can look to see what
XrdFfsWcacheFbufs[0] look like. The reason it's optimized out in future
frames is because the compiler eliminates stack frames whete i thinks it
doesn't need them and simply keeps the value in a register.
Andy
On Wed, 15 Jan 2020, Geonmo Ryu wrote:
> Unfortunately, I can not see the values due to compiler optimized.
>
> (gdb) p XrdFfsWcacheFbufs[fd]
> value has been optimized out
>
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1116#issuecomment-574999928
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1