Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "André Pönitz" <apoenitz@trolltech.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [bug] problem printing local vars in shared lib function
Date: Tue, 28 Oct 2008 18:06:00 -0000	[thread overview]
Message-ID: <4907531A.7040805@vmware.com> (raw)
In-Reply-To: <200810280907.49029.apoenitz@trolltech.com>

André Pönitz wrote:
> On Tuesday 28 October 2008 00:03:42 Michael Snyder wrote:
>> Does this sound familiar to anybody?  X86_64...
>>
>> I have a local shared library function, built with -g,
>> gdb has its symbols and can list it, step into it, step
>> within it etc.
>>
>> I can print the values of the function parameters, but
>> not the values of local (automatic) variables.  These
>> are not statics but autos on the stack.
> 
> Is this function a constructor?
> 
> If so, it sounds familiar ;-}

No, I don't think so, I believe it was an ordinary
function, and in fact I think the problem was demonstrated
to me in several different shlib functions.




      reply	other threads:[~2008-10-28 18:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-27 23:10 Michael Snyder
2008-10-28  8:08 ` André Pönitz
2008-10-28 18:06   ` Michael Snyder [this message]

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=4907531A.7040805@vmware.com \
    --to=msnyder@vmware.com \
    --cc=apoenitz@trolltech.com \
    --cc=gdb@sourceware.org \
    /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