From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>, <gdb@sourceware.org>
Cc: "'Pedro Alves'" <pedro_alves@portugalmail.pt>
Subject: RE: Our next GDB release (GDB version 6.8)
Date: Mon, 28 Jan 2008 10:56:00 -0000 [thread overview]
Message-ID: <000501c8619c$5261e940$f725bbc0$@u-strasbg.fr> (raw)
In-Reply-To: <20080126005319.GD21874@adacore.com>
I would really like to have the
call to __main fixed !
This would allow to get consistent behavior
between linux and cygwin/mingw32 for the
'start' command as skip_prologue would
really go up to the first real instruction.
Pedro proposed a patch for this,
http://sourceware.org/ml/gdb-patches/2007-10/msg00361.html
which is not perfect in the sense that it is
i386 specific, while this should be
processor independent.
But supporting this for all compilers
might require much bigger changes,
like adding a processor independent layer to
skip_prologue, that would be able to
just call process_is_call (CORE_ADDR pc, char *func_name)
that would return pc if it is not a call instruction
or the CORE_ADDR after the call instruction if pc points to a call
instruction,
and func_name would return the function name if the call
points to a existing function (the second argument type
might also be a psymbol struct, or something similar...)
This could be used for __main _alloca, but probably also
for _mcount for executables containing profiling information.
The reason this change is probably much bigger is
that it would require to add a new processor_is_call function
to the tdep struct, and restructure the skip_prologue.
Is it reasonable to hope for inclusion of this
patch before the branch?
Pierre Muller
PS: I would also like my small second patch about BINOP_INTDIV
http://sourceware.org/ml/gdb-patches/2008-01/msg00606.html
next prev parent reply other threads:[~2008-01-28 10:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 0:53 Joel Brobecker
2008-01-26 9:21 ` Eli Zaretskii
2008-01-26 13:59 ` Joel Brobecker
2008-01-26 14:14 ` Eli Zaretskii
2008-01-26 16:07 ` Joel Brobecker
2008-01-26 16:36 ` Eli Zaretskii
2008-01-26 17:00 ` Christopher Faylor
2008-01-26 17:19 ` Eli Zaretskii
2008-01-26 17:25 ` Joel Brobecker
2008-01-26 17:19 ` Joel Brobecker
2008-01-27 7:32 ` Nicholas Mc Guire
2008-01-27 15:10 ` Daniel Jacobowitz
[not found] ` <Pine.LNX.4.58.0801282316360.2555@vlab.hofr.at>
2008-01-29 13:50 ` Daniel Jacobowitz
2008-01-29 20:23 ` Eli Zaretskii
2008-01-27 17:05 ` Jim Blandy
2008-01-28 10:56 ` Pierre Muller [this message]
2008-01-28 12:35 ` Pedro Alves
2008-01-28 12:41 ` Pedro Alves
2008-01-28 17:40 ` Paul Koning
2008-01-31 14:49 ` Pedro Alves
2008-01-28 21:02 ` Thiago Jung Bauermann
2008-01-29 21:19 ` Joel Brobecker
2008-01-30 10:57 ` Markus Deuling
2008-01-30 18:32 ` Joel Brobecker
2008-01-30 23:14 ` Doug Evans
2008-01-31 0:09 ` Joel Brobecker
2008-01-31 8:15 ` Vladimir Prus
2008-01-31 16:55 ` 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='000501c8619c$5261e940$f725bbc0$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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