Skip to content
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

Empty recent.yml causes segfault #370

Closed
rroohhh opened this issue Jun 2, 2021 · 0 comments
Closed

Empty recent.yml causes segfault #370

rroohhh opened this issue Jun 2, 2021 · 0 comments

Comments

@rroohhh
Copy link
Contributor

rroohhh commented Jun 2, 2021

A empty recent.yml causes a segfault:

Thread 1 ".glscopeclient-" received signal SIGSEGV, Segmentation fault.
0x000000000046d10c in YAML::Node::Node(YAML::Node const&) ()
(gdb) bt
#0  0x000000000046d10c in YAML::Node::Node(YAML::Node const&) ()
#1  0x0000000000459b64 in OscilloscopeWindow::LoadRecentlyUsedList() ()
#2  0x0000000000464d4b in OscilloscopeWindow::OscilloscopeWindow(std::vector<Oscilloscope*, std::allocator<Oscilloscope*> > const&, bool, bool) ()
#3  0x00000000004a36b2 in ScopeApp::run(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, bool, bool, bool, bool, bool) ()
#4  0x0000000000423005 in main ()

(This can for example happen if glscopeclient crashes in the import dialog)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant