-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UsbdmFlashprogrammer segfault. #9
Comments
Hi,
|
Hi, I always do CleanAll before compille or git pull. The new debian system is a clean install without any extra CFlLAGS or so... because the Flashprogrammer and GDBServer works fine on my old debian system the problem probably related to the GCC12 or maybe to the newer wx libs also something wrong with the build system. The debug information swapped between the normal and debug versions (on both, old and new Linux) the created .deb file contains 2 different vesions and both have no debug info (but the sizes are different) bin files from the source tree: bin files from the *.deb package tree Here is the BT from the NON debug app :) Reading symbols from UsbdmFlashProgrammer... Thread 1 "UsbdmFlashProgr" received signal SIGSEGV, Segmentation fault. |
Hi, bye |
I see the access rights are not OK, changed to 644 for files... The original file list... The app starts but got this message 2 times, then start.. |
I will check the script that creates the DEB. The error reporting to user is obviously a bit poor. I use wxFormbuilder to create the dialogue skeletons. I have clicked too many buttons. It will take a while to track down where these are as I don't want to just change the C++ code as I may need to re-generate files from the .fbp files. |
Probably not so much ppl using this project under linux :) BTW, the installscripts need to be more precise about the access rights at least on the Linux distros. and also take a look why the debug/normal built swapped while compille on Linux. and ofcos thanks for the support :) |
Fix done for permissions I hope. The image created now has the permissions explicitly set in the image. I don't believe this is the correct method as there are some options you can set somewhere when building but I'm not familiar with the details. |
Everything works fine, Thank you :) |
Hi,
(Using Linux, Debian BookWoorm, latest Wx libs)
The UsbdmFlashProgrammer and the GSBServer both got segfault at same point.
firmware loader (HCS), FlashDump app works fine...
BackTrace of Flasprogrammer:
Reading symbols from UsbdmFlashProgrammer-debug...
(No debugging symbols found in UsbdmFlashProgrammer-debug)
(gdb) run
Starting program: /opt/src/usbdm_4.12.1.300-1-x86_64/usr/bin/UsbdmFlashProgrammer-debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff15866c0 (LWP 31615)]
[New Thread 0x7ffff0d856c0 (LWP 31616)]
[New Thread 0x7fffebfff6c0 (LWP 31617)]
Thread 1 "UsbdmFlashProgr" received signal SIGSEGV, Segmentation fault.
0x00007ffff7f6b54c in ?? () from /usr/lib/x86_64-linux-gnu/usbdm/libusbdm-device-database-debug.so.4
(gdb) bt
#0 0x00007ffff7f6b54c in ?? () from /usr/lib/x86_64-linux-gnu/usbdm/libusbdm-device-database-debug.so.4
#1 0x00007ffff7f6b597 in ?? () from /usr/lib/x86_64-linux-gnu/usbdm/libusbdm-device-database-debug.so.4
#2 0x00007ffff7f65db6 in DeviceDataBase::getDefaultDevice() ()
from /usr/lib/x86_64-linux-gnu/usbdm/libusbdm-device-database-debug.so.4
#3 0x00007ffff7f67e6e in DeviceDataBase::loadDeviceData() ()
from /usr/lib/x86_64-linux-gnu/usbdm/libusbdm-device-database-debug.so.4
#4 0x00005555555c8190 in ?? ()
#5 0x00005555555c70a1 in ?? ()
#6 0x00005555555c76b5 in ?? ()
#7 0x00005555555bd49d in ?? ()
#8 0x00005555555bc2d9 in ?? ()
#9 0x00007ffff72a306b in wxAppConsoleBase::OnInit() () from /lib/x86_64-linux-gnu/libwx_baseu-3.2.so.0
#10 0x00005555555bb953 in ?? ()
#11 0x00005555555c4adf in ?? ()
#12 0x00007ffff731feea in wxEntry(int&, wchar_t**) () from /lib/x86_64-linux-gnu/libwx_baseu-3.2.so.0
#13 0x00005555555bae3e in ?? ()
#14 0x00007ffff704618a in __libc_start_call_main (main=main@entry=0x5555555bae1c, argc=argc@entry=1,
argv=argv@entry=0x7fffffffdff8) at ../sysdeps/nptl/libc_start_call_main.h:58
#15 0x00007ffff7046245 in __libc_start_main_impl (main=0x5555555bae1c, argc=1, argv=0x7fffffffdff8,
init=, fini=, rtld_fini=, stack_end=0x7fffffffdfe8)
at ../csu/libc-start.c:381
#16 0x0000555555580501 in ?? ()
(gdb)
The text was updated successfully, but these errors were encountered: