Replies: 5 comments 1 reply
-
Hmm, using call_external on a new architecture, how brave! |
Beta Was this translation helpful? Give feedback.
-
Thanks for the hint. I will try!
… On 20. Oct 2022, at 04:58, Giloo ***@***.***> wrote:
Hmm, using call_external on a new architecture, how brave!
A sudden segmentation fault when creating a new array variable during the parsing of a command line --- the most common operation made in GDL ... I would say this is indeed due to the c-program called somehow making a mess in another part of memory.
Which in turn may eventually point to a bug in GDL, who knows, new architectures are good to find defects in programs...
This can be hard to debug, unless it crashes always at the same command line.
If valgrind works on aarch64, it perhaps could tell what memory was crushed, by what part of (C?) code.
—
Reply to this email directly, view it on GitHub <#1382 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOC5K6G4DHLBMRO6W6XTAFTWED3SFANCNFSM6AAAAAARJRSIQI>.
You are receiving this because you authored the thread.
|
Beta Was this translation helpful? Give feedback.
-
Hi folks, I run my program with valgrind and got a 90000 lines report of memory leaks and so on.
Can anybody have a quick look on it and give me a hint on what to do next?
|
Beta Was this translation helpful? Give feedback.
-
Thanks. If possible you can remove the attached valgrind_segfault.txt First there is a memory leak in smooth.cpp that must be solved. The large number of small loss memory in objects.cpp is probably unavoidable given the code There is also a small leak problem in open_lun (?) first time I see that. But this does not IMHO explain the crash. There is no hint of a memory corruption which would appear along with the keyword "allocated" (if I'n not mistaken). |
Beta Was this translation helpful? Give feedback.
-
Thanks! |
Beta Was this translation helpful? Give feedback.
-
I have a new Mac Studio with Suse aarch64 and I run my software as usual but now I get segfault (sometimes):
Magick: abort due to signal 11 (SIGSEGV) "Segmentation Fault"...
Aborted (core dumped)
The GDL program uses a call_external and I think the c-program that it is calling causes the segfault but I have no idea on how to debug further.
I run with gdb and get following hints:"
How can I debug further?
Who can help me?
Beta Was this translation helpful? Give feedback.
All reactions