Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb@sourceware.org>
Subject: Re: sizeof evaluates expression to compute size?
Date: Thu, 17 Sep 2015 14:10:00 -0000	[thread overview]
Message-ID: <20150917140949.GA2332@jaguar.corp.atmel.com> (raw)
In-Reply-To: <20150916145632.GA19688@adacore.com>

On Wed, Sep 16, 2015 at 07:56:32AM -0700, Joel Brobecker wrote:
> >   Is it true that gdb evaluates the expression in a "print
> >   sizeof(expression)" to figure out the size?
> 
> Yes; it actually evaluates the entire expression (including the use
> of the sizeof operator).
> 
> >   For one expression on the ARM target 
> > 
> >      print sizeof((char*)(s->m)
> 
> The expression is incomplete; but with the expression you gave and
> assuming we're just missing a closing parenthesis, I don't see why
> it would need to allocate memory in the inferior. Perhaps you've found
> a bug.

Here's a more complete testcase.

typedef struct tagFoo
{
    int x;
    char arr[10];
} Foo;

Foo *pFoo;
int main()
{
  return 1;
}

Compiling with
$ gcc test.c -O0 -g3

and then starting gdb (native x86_64, v7.10) gives
$ gdb a.out
>>> print sizeof((char*)pFoo->arr) 
evaluation of this expression requires the target program to be active

Starting the program, putting a breakpoint on malloc, and then executing
the above command  causes the breakpoint to be hit.

Evaluation works fine without the cast to char*
>>> print sizeof(pFoo->arr)
$2 = 10

Should I file a bug?

Regards
Senthil


  reply	other threads:[~2015-09-17 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 14:41 Senthil Kumar Selvaraj
2015-09-16 14:56 ` Joel Brobecker
2015-09-17 14:10   ` Senthil Kumar Selvaraj [this message]
2015-09-17 14:19     ` Joel Brobecker

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=20150917140949.GA2332@jaguar.corp.atmel.com \
    --to=senthil_kumar.selvaraj@atmel.com \
    --cc=brobecker@adacore.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