Active Topics
-
Re-commissioning N9 in 2018 (125)
to MeeGo / Harmattan by Boxeri - 1 hr, 28 mins ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 11 hrs, 59 mins ago -
List of well performing apps on Leste (33)
to Maemo 7 / Leste by teroyk - 20 hrs, 30 mins ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 2 days ago -
Maemo repository (4)
to Community by teroyk - 3 days, 21 hrs ago -
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 5 days, 3 hrs ago -
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 5 days, 12 hrs ago - more...
|
2013-04-20
, 14:06
|
|
Posts: 3,074 |
Thanked: 12,964 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#292
|
Originally Posted by avidscavenger
You are missing debug symbols for /usr/lib/libQtCore.so.4, that is why gdb says "Backtrace stopped: previous frame identical to this frame (corrupt stack?)". Just install libqt4-core-dbg and you'll see. I can't say it clearer than that
Thanks.
Unfortunately doesn't really tell me what I didn't already know. Two valid stack frames then nothing but question marks. Some buffer over- or under-run has destroyed the stack? Any suggestions?
Note that turning off compiler optimisation makes the problem go away. And valgrind didn't find anything.
Not too sure where to go from here.
__________________
Never fear. I is here.
720p video support on N900,SmartReflex on N900,Keyboard and mouse support on N900
Nothing is impossible - Stable thumb2 on n900
Community SSU developer
kernel-power developer and maintainer
Never fear. I is here.
720p video support on N900,SmartReflex on N900,Keyboard and mouse support on N900
Nothing is impossible - Stable thumb2 on n900
Community SSU developer
kernel-power developer and maintainer
| The Following 5 Users Say Thank You to freemangordon For This Useful Post: | ||
|
|
2013-04-20
, 23:08
|
|
Posts: 96 |
Thanked: 80 times |
Joined on May 2010
|
#293
|
Originally Posted by freemangordon
That is what I did.
You are missing debug symbols for /usr/lib/libQtCore.so.4, that is why gdb says "Backtrace stopped: previous frame identical to this frame (corrupt stack?)". Just install libqt4-core-dbg and you'll see. I can't say it clearer than that
Here is some output:
Code:
user@Nokia-N900:~/MyDocs/core-dumps/columbus-3E77-11-2005$ dpkg -l libqt4-core-dbg Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=====================-=====================-========================================================== ii libqt4-core-dbg 1:4.7.4~git20110505+c Qt 4 library debugging symbols user@Nokia-N900:~/MyDocs/core-dumps/columbus-3E77-11-2005$ gdb /opt/usr/bin/columbus ./coredump GNU gdb (GDB) 6.8.50.20090417-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabi". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... (no debugging symbols found) Reading symbols from /opt/usr/lib/librxsupport.so.1...(no debugging symbols found)...done. Loaded symbols for /opt/usr/lib/librxsupport.so.1 Reading symbols from /opt/usr/lib/libcolumbus.so.1...(no debugging symbols found)...done.
Code:
Reading symbols from /usr/lib/libQtCore.so.4...Reading symbols from /opt/usr/lib/debug/usr/lib/libQtCore.so.4.7.4...done. done. Loaded symbols for /usr/lib/libQtCore.so.4
Code:
Core was generated by `/opt/usr/bin/columbus'.
Program terminated with signal 11, Segmentation fault.
#0 QString::fromLatin1_helper (str=0x73 <Address 0x73 out of bounds>, size=-1) at tools/qstring.cpp:3743
3743 tools/qstring.cpp: No such file or directory.
in tools/qstring.cpp
(gdb) bt
#0 QString::fromLatin1_helper (str=0x73 <Address 0x73 out of bounds>, size=-1) at tools/qstring.cpp:3743
#1 0x40e7910c in QString::fromAscii_helper (str=0x73 <Address 0x73 out of bounds>, size=1088917772)
at tools/qstring.cpp:3809
#2 0x00015ad0 in ?? ()
#3 0x00015ad0 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Current language: auto; currently c++
(gdb)
|
|
2013-04-20
, 23:17
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#294
|
[OT] @avidscavenger: southern hemisphere + good command of English: OZ, NZ, SA?
HA (ex SA)
HA (ex SA)
| The Following 3 Users Say Thank You to handaxe For This Useful Post: | ||
|
|
2013-04-20
, 23:26
|
|
Posts: 96 |
Thanked: 80 times |
Joined on May 2010
|
#295
|
Originally Posted by handaxe
If you consider Australian English to be good English
[OT] @avidscavenger: southern hemisphere + good command of English: OZ, NZ, SA?
HA (ex SA)
|
|
2013-04-20
, 23:30
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#296
|
Originally Posted by avidscavenger
Honest mistake!
If you consider Australian English to be good English
| The Following 2 Users Say Thank You to handaxe For This Useful Post: | ||
|
|
2013-04-21
, 01:26
|
|
Posts: 96 |
Thanked: 80 times |
Joined on May 2010
|
#297
|
@handaxe - also OT but I can't find any threads that mention this. Since I included community-testing among my repos and did an upgrade, my hald_addon_bme has stopped working. That is, when I plug my phone into a USB source it doesn't give a pop-up message and start charging at 500mA/1000mA depending on the source. Instead it just charges at 100mA and I have to manually tweak the charge rate. Any clues?
| The Following User Says Thank You to avidscavenger For This Useful Post: | ||
|
|
2013-04-21
, 09:08
|
|
Posts: 3,074 |
Thanked: 12,964 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#298
|
Originally Posted by avidscavenger
Phew, finally :P.
That is what I did.
Here is some output:
<snip>Code:user@Nokia-N900:~/MyDocs/core-dumps/columbus-3E77-11-2005$ dpkg -l libqt4-core-dbg Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=====================-=====================-========================================================== ii libqt4-core-dbg 1:4.7.4~git20110505+c Qt 4 library debugging symbols user@Nokia-N900:~/MyDocs/core-dumps/columbus-3E77-11-2005$ gdb /opt/usr/bin/columbus ./coredump GNU gdb (GDB) 6.8.50.20090417-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabi". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... (no debugging symbols found) Reading symbols from /opt/usr/lib/librxsupport.so.1...(no debugging symbols found)...done. Loaded symbols for /opt/usr/lib/librxsupport.so.1 Reading symbols from /opt/usr/lib/libcolumbus.so.1...(no debugging symbols found)...done.
<snip>Code:Reading symbols from /usr/lib/libQtCore.so.4...Reading symbols from /opt/usr/lib/debug/usr/lib/libQtCore.so.4.7.4...done. done. Loaded symbols for /usr/lib/libQtCore.so.4
As you can see, we get a bit more information about the line numbers and variable names, but nothing more on the stack.Code:Core was generated by `/opt/usr/bin/columbus'. Program terminated with signal 11, Segmentation fault. #0 QString::fromLatin1_helper (str=0x73 <Address 0x73 out of bounds>, size=-1) at tools/qstring.cpp:3743 3743 tools/qstring.cpp: No such file or directory. in tools/qstring.cpp (gdb) bt #0 QString::fromLatin1_helper (str=0x73 <Address 0x73 out of bounds>, size=-1) at tools/qstring.cpp:3743 #1 0x40e7910c in QString::fromAscii_helper (str=0x73 <Address 0x73 out of bounds>, size=1088917772) at tools/qstring.cpp:3809 #2 0x00015ad0 in ?? () #3 0x00015ad0 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Current language: auto; currently c++ (gdb)
Now, you have 2 options from here:
1. Start application, attach gdb and wait it to SEGFAULT.
2. Start application, start gdb, load the coredump and attach to the application
Either will work and will give you the real backtrace.
BTW I am on #maemo IRC @ freenode.net, better join there to speedup the communication.
__________________
Never fear. I is here.
720p video support on N900,SmartReflex on N900,Keyboard and mouse support on N900
Nothing is impossible - Stable thumb2 on n900
Community SSU developer
kernel-power developer and maintainer
Never fear. I is here.
720p video support on N900,SmartReflex on N900,Keyboard and mouse support on N900
Nothing is impossible - Stable thumb2 on n900
Community SSU developer
kernel-power developer and maintainer
 |
|
2013-04-21
, 12:00
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#299
|
Originally Posted by freemangordon
[OT]I would rather suggest #maemo-alternatives - this was the channel, where I managed to get freemangordon's attention to this thread, and, in particular, to coredump interpretation problems.
BTW I am on #maemo IRC @ freenode.net, better join there to speedup the communication.
Official #maemo channels got one pesky, ego-problems focused admin, who lately feels very trigger-happy to ban people (probably, due to feeling like owning Maemo Community and being irreplaceable, thanks to some politic twists).
#maemo-alternatives sounds like better place for friendly, uncensored discussion - channel is managed by normal, responsible people. While originally meant to discuss alternative (to #maemo) operating systems on N900, lately it started to become alternative to "official" maemo channels (that were hostily taken over, long time ago) as a whole, and #maemo-alternatives staff doesn't have anything against it (AIUI).
Just suggestin' [/OT]
/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
Last edited by Estel; 2013-04-21 at 12:04.
| The Following User Says Thank You to Estel For This Useful Post: | ||
|
|
2013-04-21
, 12:18
|
|
Posts: 1,378 |
Thanked: 1,604 times |
Joined on Jun 2010
@ Göteborg, Sweden
|
#300
|
@estel: can you help avidscavenger with his question about charging? I admit I get confused as to the bme replacement status.
EDIT: bme replacement is not yet distributed but available for testing on Pali's site.
AFAIK, that is a kernel-power issue, and charging works for me with kp52. Unclear whether avidscavenger has kp installed. Could CSSU-T interfere with charging? Bad install?
Stay cool on the comments
PS looking at his post, he may have installed via apt.
Last edited by handaxe; 2013-04-21 at 18:44.
EDIT: bme replacement is not yet distributed but available for testing on Pali's site.
AFAIK, that is a kernel-power issue, and charging works for me with kp52. Unclear whether avidscavenger has kp installed. Could CSSU-T interfere with charging? Bad install?
Stay cool on the comments
PS looking at his post, he may have installed via apt.
Last edited by handaxe; 2013-04-21 at 18:44.
 |
| Tags |
| navigation, nokia n900 |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 07:57.
Unfortunately doesn't really tell me what I didn't already know. Two valid stack frames then nothing but question marks. Some buffer over- or under-run has destroyed the stack? Any suggestions?
Note that turning off compiler optimisation makes the problem go away. And valgrind didn't find anything.
Not too sure where to go from here.