[Anonymous]

@opiswahn wrote:

Hi,

i am trying to build a program for an stm32f3 with c++ code. So far so good. But when i try to use a map(std::map m_PortMap), i get this compile error:
“error VGDB1000: undefined reference to ‘__exidx_end'”
“error VGDB1000: undefined reference to ‘__exidx_start'”
in the file unwind-arm-common.inc

I have no idea whats the problem here, can someone make something out of this?

Greets,

**Jürgen**

Hi Jurgen,

It looks like you are missing the below from your linker script:

.ARM.exidx :
{
__exidx_start = .;
*(.ARM.exidx* .gnu.linkonce.armexidx.*)
__exidx_end = .;
} > rom

Make sure you change “rom” to whatever alias you use for your FLASH area. The reason why you need that is because you are linking to libstdc++.a and that lib stores some of its code/data in the “.ARM.exidx” section. Hope that helps.

[Anonymous]

@bazis wrote:

Please also note that if you program your project starting at 64KB using VisualGDB, it will fill the first 64KB with zeroes and not just keep them unchanged.

Hi Bazis,

Thank you for responding. So basically it does a full chip erase before programming? If that is the case, it won’t work with my situation. In my case, a complete firmware consists of 3 different firmwares that reside in different area in flash that works together: pre-bootloader, bootloader, and application. When the device starts, it runs the pre-bootloader that decides whether to jump to the application or the bootloader depending on some physical switch buttons configuration. With that said, when I debug the application project (using the application .elf file), I want to erase just the sectors after 64kb from 0x08000000 (yes, i am using stm32f407) leaving the pre-bootloader and bootloader in place, program the application into flash, then start debugging.

Right now we are using Insight Debugger/Eclipse CDT and we can do what I just described without any issue. But it’s just not convenient to use multiple tools for programming, compiling, and debugging. Let me know if there is any way around this issue with VisualGDB. Thanks!!!

[Anonymous]

Ok, I’ve tried it and it works. Thanks!
Now, I was wondering if the compiler optimizations are the same for armv6(raspberry) and armv7(BBB). Are they?

More thanks for the support.

[Anonymous]

I have the same issue for local project headers is it possible to have the same kind a variable for it?

Damien

[Anonymous]

You have right, what i need to say? We are on the same boat.

[Anonymous]

Thanks for the response, Ket. So far, my attempts to get Qt working on Android via VS2010 (with or without VisualGDB) have all failed to build. I have ultimately, however, been able to get my same source trees to build under QtCreator. I don’t know if we could learn anything by dissecting the build directories or other info from that.

[Anonymous]

Yeah must wait ok, but for how many days-months-years?
I have see your thread, was oct 2012, now is nov 2013 and no answer, so?

[Anonymous]

visualgdb remote console.

[Anonymous]

Hi ket,

I have updated “gdb” to latest version :

GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 

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 "armv5tejl-unknown-linux-gnueabi".

For bug reporting instructions, please see:

.

Now all working very very well …

Your tool is really fantastic … compliments.

Thanks very much.

debugasm

[Anonymous]

Thank you

[Anonymous]

Hi,

First of all, try updating your gdbserver, the 2009 year version is probably a bit old. If your gdb is as old, try updating that as well.

I will try to update it 🙄 …

The problem with the predebug command can be the working directory, try clearing that field.

I have clearing that field but the problem remainig :

VisualGDB: Executing predebug actions
VisualGDB: Run "killall --quiet gdbserver" in directory "" on root@192.168.1.199 (SSH)

Command exited with code 1
Executable: killall
Arguments: --quiet gdbserver
Directory:
VisualGDB: Error: Command-line action failed

Any other ideas ?

The debug app startup button is grayed as it is only used for Android app projects, it is a special debug option allowing to connect gdb gracefully while pausing the Java code execution.

I thought it was also used for C / C++ code.

Thanks very much.

debugasm

[Anonymous]

Man don’t get angry…we can’t do nothing. I have opened a thread several time ago:

forum.sysprogs.com/viewtopic.php?f=3&t=2439

I’m always wait for an answer, he just do a couple of thing ( and one of those is eject the iso and not the drive ) and i don’t think require weeks of work, my opinion, but he is the only can do it no other can, the code is open-source but is unreadable and incompilable for anyone except basiz. Must wait.

[Anonymous]

Hi,

I have made some others test but without good results. I have disabled all debug windows but problem remain (#### First Test ####) :

On my remote machine gdbserver is :

GNU gdbserver (GDB) 7.0.1-debian
Copyright (C) 2009 Free Software Foundation, Inc.
gdbserver is free software, covered by the GNU General Public License.
This gdbserver was configured as "arm-linux-gnueabi"

I start the debug sessione with “Start Debugging With GDB” :

To continue I need to press to “Abort Command” :

And debug start without problem “F10” and “F11” work.

For others test on #### Second Test #### :

I added the custom command before starting the debugging session :

I start the debugger but generate one error :

And the log is empty, how to see what the problem is ?

Why the rapid button is grayed ?

Thanks very much for your help.

debugasm

[Anonymous]

I tried your suggestion of using %PROGRAMFILES(x86)%, and it will not accept it unless I then press “Detect”, at which point it simply expands the variable to “Program Files(x86)”. Then the code will no longer build. The change I was suggesting was simply something that would pass the variables to ANT in some intact manner so that these error do not come up. Otherwise, I would simply suggest that the tutorial explain that all 4 of the dependencies (SDK, NDK, ANT, and JDK) must be installed in non-space directories, even if this requires re-installation. This might save potential users a lot of time. Thanks for the help!

[Anonymous]

Hi,

For the first issue, if you have a disassembly window open, then close it. That usually makes gdb query those strange hex symbols. There is no way to stop the “GDB Command Timeout” window from appearing as it only appears if there are problems with commands taking too long. The window will close automatically if the command manages to complete, if not then it provides the user a way to abort the command or even stop debugging. If the window would not appear, then in the case of commands never completing, debugging will hang indefinitely with no info on why.

I do not have “disassembly window” open but I have “Memory” display open, I do some other test disabling everything.

… You can add an action to kill the gdbserver manually to either pre or post GDB actions (Custom debug steps page in VisualGDB Project Properties). You can also try killing gdb by setting the stop debugging action differently (bottom of GDB Settings page in VisualGDB Project Properties). Also, you switch to using a custom gdb stub from Debug settings (“start gdb in the following mode”) to specify additional gdbserver settings.

Thanks for info, I’ll try as you suggested.

Thanks very much.

debugasm

[Author]

Posts