El lun, 01-03-2010 a las 20:48 +0000, modest.me...@spamgourmet.com
escribió:
> (gdb) run -s
> Starting program: /home/mat/modest/modest/modest-3.1.18+0m5/src/modest
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00828361 in __do_global_dtors_aux ()
> 0x00828361 <__do_global_dtors_aux+81>: mov (%eax),%edx
>
> Why doesn't the compiled binary work?
>
> So instead I'm doing the entire "dpkg-buildpackage -rfakeroot -uc -b -d"
> thing and installing the packages, then trying to debug those. That's
> horribly inefficient (it has to rebuild from scratch every time, and do
> it in both normal and debug modes). Is that really what I have to do?
Maybe the problem is that, building with debian scripts, it will run
modest with maemo launcher support. This means that modest will be
harder to debug, and you won't be able to run directly the binary.
The way to run the binary, in fact, is a bit different if maemo
launcher support is done. What I do is:
run-standalone.sh native-gdb --args maemo-summoner modest.launch -s
Explanation about these:
* modest.launch: the modest binary itself as installed with debian
package. This one is as a shared library that's run by maemo launcher.
* maemo-summoner: a program that emulates the behavior of maemo
launcher, loading just one "launch" binary.
* native-gdb: a script that helps you run the proper gdb instead of
scratchbox one (equivalent to the trick Sergio told). This is in package
maemo-debug-scripts.
--
José Dapena Paz <jdap...@igalia.com>
Igalia
_______________________________________________
Modest-devel mailing list
Modest-devel@garage.maemo.org
https://garage.maemo.org/mailman/listinfo/modest-devel
