Now this looks cool (except for the "stopped at file..." thing)! :)
I don't quite understand your question about /opt/e17. If you just want to
install it you just add it to Makefile.am like you would do any other data
file (look at efl/data if you don't know how for some reason). The problem
is th
Hey Tom,
You are right. Don't tell me "I know, I am always right!" ;-)
Following the script.
Next step, how can I install it in /opt/e17? Which file do I need to modify?
Script:
class Eo_step(gdb.Command):
def __init__(self):
gdb.Command.__init__(self, "eo_step", gdb.COMMAND_OBSCURE)
Hey Daniel,
I found this in python.c in the gdb source tree:
/* Implementation of gdb.solib_name (Long) -> String.
Returns the name of the shared library holding a given address, or None. */
static PyObject *
gdbpy_solib_name (PyObject *self, PyObject *args)
So just use gdb.solib_name...
I
Hi Tom,
1. I will check it, maybe just print line and which file
2. I don't find how to get the library name. Sure it will be easier with
the library.
3. I understand the point but for the moment I don't have a solution. I
will investigate when time is with me (not so english, this sentence).
I
Hey Daniel,
Good thing that it works and I'm happy you improved it so fast, but I still
have a couple of comments:
1. "print "You reached the function " +
str(gdb.selected_frame().function())" - It's probably better to change it
to fit the gdb style of info messages better. It doesn't look like
so
Hi Tom,
It works with stepi.
The stepping process consists now in two phases:
- stepping until we are no more in the the caller function
- stepping while function name unknown or still in Eo.c (yes I stay with
that, it seems easier than with the library)
It now supports Eo with and without symbo
Just use "stepi", that one goes inside. "step" goes to the next line of
code and if there is none inside it just steps to the next line. I'm
actually trying to look for a command that does what I said we need in the
first place (and that you've implemented to some extent), which just goes
on until
On Thursday, December 6, 2012, daniel.za...@samsung.com wrote:
> Hi Gustavo,
>
> I think the problem with adding flags is the performance.
A single Boolean check is nothing compared to everything else. And it's
once per eo_do() not per subcall
> eo_do is the
> most called function in Eo (wit
Hi Gustavo,
I think the problem with adding flags is the performance. eo_do is the
most called function in Eo (with eo_data_get) and we need it fast. More,
you know what the functions parameters are, you called it. So in my
opinion, the most important thing is what the destination is.
Did you
When I compile without -O and -g, gdb behaves like with stripped
library, i.e doesn't try to enter the function. Maybe I do something wrong.
Tom, can you try it on your computer?
Thank you
Daniel
On 12/06/2012 12:45 AM, Tom Hacohen wrote:
> Compile Eo in release mode: remove -O0/-g from your CFL
Compile Eo in release mode: remove -O0/-g from your CFLAGS, re-configure Eo
(efl tree I assume) with --with-profile=release (or something like that,
just check the configure options, it's easy) and make && make install. You
can potentially just strip the binary, doesn't matter really...
On Wed, D
On Wed, Dec 5, 2012 at 1:52 PM, daniel.za...@samsung.com
wrote:
> Tom, the 'sudo strip -g libeo.so' on my computer prevents me to see info
> about this library in gdb, as explained before. How can I compile Eo in
> release mode?
>
> Gustavo, this could be very useful. We need to check if it really
Tom, the 'sudo strip -g libeo.so' on my computer prevents me to see info
about this library in gdb, as explained before. How can I compile Eo in
release mode?
Gustavo, this could be very useful. We need to check if it really can be
done and if it is easy for the user. Is the eo_do_step supposed
Gustavo,
Your suggestion is good (I already told you that in the past, I think), but
I believe it's unrelated to what we are trying to achieve here. What I want
is an easy way to step into an eo_do function, just like we would have done
with any other function.
What I really want to see is just "
Sure, but we still need to do what we need to do. We need to be able to
only blame the gcc guys, ourselves as well.
As for the thing you said about gdb and step, that's bad, but also very
weird. GDB lets you do assembly debugging as well (not just C) in which
case having debug symbols means nothin
Let me jump in, proposing here what I already proposed earlier at IRC
and in person during LinuxCon-EU:
we should use the same debug helper way as gcc does for itself.
GCC is built on top of an union of every possible AST node. So
functions, variables, loops... are all into the same type/union,
m
Hi all,
I don't need to reply, but to thank you and give you respect, I feel
that I must reply ;-) When I strip Eo library, I cannot in gcc step into
at all, I mean, I can't reach the final destination. It is like the
'skip' feature of gdb. So for the moment, I am stuck with that filename
and
Cool. And we already talked a bit more on IRC about the usage of the binary
name vs. the source file name, so I'm happy, no need for your reply here.
On 5 Dec 2012 05:16, "daniel.za...@samsung.com"
wrote:
> Hey Tom,
>
> I saw your mail, I just wanted to explain SeoZ how to do now until I put
> it
Hey Tom,
I saw your mail, I just wanted to explain SeoZ how to do now until I put
it there automatically. I will change the name to eo_step.
I know this site, I don't know yet which way to use to configure gdb.
For the moment, I create manually a .gdbinit in my home directory and
there source t
Daniel,
It should be installed (as I've said before) see
http://sourceware.org/gdb/onlinedocs/gdb/Python.html for more info.
Then it'll be just a matter of loading the script and using it (or possibly
it'll get loaded automatically). Also, as I said, I think eo_jump is a
terrible name and it shoul
No it doesn't. Sorry for the "..." I overuse it lately, don't know why. I
just mentioned it as something to remember, i.e that putting it there is
not enough, it should be installed as well.
On Tue, Dec 4, 2012 at 12:20 PM, Vincent Torri wrote:
> On Tue, Dec 4, 2012 at 12:11 PM, Tom Hacohen wro
On Tue, Dec 4, 2012 at 12:11 PM, Tom Hacohen wrote:
> It's a gdb plug-in that should be installed...
and ? Does this forbid to put that in the dir i mentioned ?
Vincent
>
>
> On Tue, Dec 4, 2012 at 10:46 AM, Vincent Torri wrote:
>
>> On Tue, Dec 4, 2012 at 11:39 AM, Tom Hacohen wrote:
>> > Oh
You open gdb and you paste the function (from python to end) there.
After, when you encounter a eo_do function, instead of stepping into it,
you call the function (just type eo_jump) and it will do the job alone
and reach the function that you wanted.
On 12/04/2012 10:54 AM, Daniel Juyung Seo w
Oh, btw, please rename it to eo_step which better explains what it does.
On Tue, Dec 4, 2012 at 11:11 AM, Tom Hacohen wrote:
> It's a gdb plug-in that should be installed...
>
>
> On Tue, Dec 4, 2012 at 10:46 AM, Vincent Torri wrote:
>
>> On Tue, Dec 4, 2012 at 11:39 AM, Tom Hacohen wrote:
>>
It's a gdb plug-in that should be installed...
On Tue, Dec 4, 2012 at 10:46 AM, Vincent Torri wrote:
> On Tue, Dec 4, 2012 at 11:39 AM, Tom Hacohen wrote:
> > Oh cool, I'm glad you are already done, but as I told you before:
> > 1. don't rely on the source filename (eo.c) as this information ma
On Tue, Dec 4, 2012 at 11:39 AM, Tom Hacohen wrote:
> Oh cool, I'm glad you are already done, but as I told you before:
> 1. don't rely on the source filename (eo.c) as this information may not be
> available for most people, you must rely on the soname.
> 2. Please commit it to svn and make it sh
Oh cool, I'm glad you are already done, but as I told you before:
1. don't rely on the source filename (eo.c) as this information may not be
available for most people, you must rely on the soname.
2. Please commit it to svn and make it ship/install automatically for
people that install the efl.
Ch
Awesome
I and co-workers have hard time to debug with eo.
This looks very good but how can I use it?
Daniel Juyung Seo (SeoZ)
On Tue, Dec 4, 2012 at 5:15 PM, daniel.za...@samsung.com <
daniel.za...@samsung.com> wrote:
> Hi all,
>
> I am sure you faced difficulties to debug your program due t
Hi all,
I am sure you faced difficulties to debug your program due to changes
with Eo. It is hard to know which function will be called by eo_do or
eo_do_super because of inheritance.
I have written a python function for gdb that helps a lot. The command
is eo_jump, no arguments.
You can execu
29 matches
Mail list logo
