| lubot_ | [telegram] <RikMills> Any suggestions on how to debug? : https://matterbridge.lubuntu.me/168e925a/file_2174.jpg | 17:41 |
|---|---|---|
| lubot_ | [telegram] <RikMills> Command line just gives back Aborted (core dumped) | 17:42 |
| lubot_ | [telegram] <mitya57> Is it possible to run it in gdb? (re @RikMills: Command line just gives back Aborted (core dumped)) | 18:00 |
| lubot_ | [telegram] <RikMills> https://matterbridge.lubuntu.me/a5e35771/file_2176.jpg | 18:05 |
| lubot_ | [telegram] <mitya57> gdb python3, then run /usr/bin/ubiquity (or whatever its name is) | 18:06 |
| fvogt | Memory corruption -> valgrind | 18:06 |
| lubot_ | [telegram] <mitya57> That's an even better suggestion. In that case valgrind python3 /usr/bin/ubiquity | 18:06 |
| lubot_ | [telegram] <RikMills> wtf? with valgrind it ran and did not crash | 18:11 |
| lubot_ | [telegram] <mitya57> But maybe there are still warnings in valgrind output? | 18:11 |
| lubot_ | [telegram] <mitya57> valgrind uses its own malloc implementation, so it won't crash with same error as without valgrind. | 18:12 |
| lubot_ | [telegram] <RikMills> Looks like I need to install debugging symbols anyway. I will have to come back to this in a couple of hrs | 18:12 |
| lubot_ | [telegram] <RikMills> Thanks :) | 18:12 |
| lubot_ | [telegram] <mitya57> Yes, debugging symbols will be useful in any case. | 18:12 |
| lubot_ | [telegram] <RikMills> https://paste.ubuntu.com/p/nWfVccZFpW/ | 18:17 |
| lubot_ | [telegram] <RikMills> will try with symbols later | 18:17 |
| fvogt | PYTHONMALLOC=malloc should help, most of that is noise | 18:19 |
| lubot_ | [telegram] <mitya57> fvogt says the right thing again :) Anyway having debug symbols for Python won't hurt. | 18:21 |
| lubot_ | [telegram] <RikMills> that just gets me aborted (core dumped) and no output | 18:23 |
| lubot_ | [telegram] <RikMills> back later. thanks :) | 18:25 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
