Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH,tests] Run to main before doing any tests in structs3.exp
Date: Wed, 07 Nov 2012 00:26:00 -0000	[thread overview]
Message-ID: <20121107002611.GD5103@adacore.com> (raw)
In-Reply-To: <50995C16.2060507@codesourcery.com>

> Consider, for example, a target that runs on QEMU. QEMU won't start
> the binary in exactly the same way as gdbserver running on linux.
> Thus, global variable initialization procedures may not have
> happened at that point yet. Consider that we start even before the
> dynamic loader had a chance to run and do all the relocation magic.

The part I don't get is why this even enters the picture. If it was
a C++ program, with elaboration code that's run when the binary is
loaded in memory, I would understand. But this is a plain C program,
where I imagine the variables are simply located in data, with their
default value provided there. So, even if the program hasn't started
at all, GDB should be able to fetch it from the binary.

That being said, I don't want to hold your patch. I think it's fine
to run the program till main. I was just curious as to why this was
sometimes necessary. Still can't get it :-).

-- 
Joel


  parent reply	other threads:[~2012-11-07  0:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-06 17:09 Luis Machado
2012-11-06 17:30 ` Joel Brobecker
2012-11-06 18:51   ` Luis Machado
2012-11-06 19:12     ` Pedro Alves
2012-11-06 20:20       ` Luis Machado
2012-11-07  0:26     ` Joel Brobecker [this message]
2012-11-07 11:24       ` Luis Machado
2012-11-07 15:09         ` Joel Brobecker
2012-11-14 19:22           ` Luis Machado

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=20121107002611.GD5103@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lgustavo@codesourcery.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