Dear Markus,
On 08/31/16 21:22, Markus Unterwaditzer wrote:
> On Wed, Aug 31, 2016 at 09:07:21PM +0200, Markus Unterwaditzer wrote:
>> On Wed, Aug 31, 2016 at 03:52:36PM +0200, Paul Menzel wrote:
>>> On 08/30/16 19:32, Markus Unterwaditzer wrote:
>>>
>>>> On Tue, Aug 30, 2016 at 01:30:20PM +0200, Paul Menzel wrote:
>>>>>> None.
>>>>>
>>>>> How do you start dwm?
>>>>
>>>> A simple `dwm` in `.xinitrc`. You can view the entire setup here:
>>>> https://github.com/untitaker/dotfiles
>>>
>>> Did you already try running dwm under GDB? You could add it to the
>>> `.xinitrc` file and attach to GDB remotely I guess.
>> Well, I have tried now! Attached is the entire session.
>>
>> I'm not sure what to look for. In another session I noticed that shortly before
>> `drw_text` gets called `text` being a nullpointer. It appears that the code is
>> designed to deal with this though.
>>
>> By the way, this time I reproduced this issue using:
>>
>> echo -e "\xe2\x9b\x93b" | xargs xsetroot -name
>>
>> Thanks for your help,
>> Markus
>
> Sorry, forgot the actual attachment. Here it is.
No problem. Thank you very much for that. Unfortunately, I won’t have
time until the end of the week to look more into it.
If you have time until then, could you please also run the process under
Valgrind, or build the stack with some sanitizers (address, undefined
behavior)?
```
$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind \
-v \
--tool=memcheck \
--leak-check=full \
--num-callers=40 \
--log-file=valgrind.log \
$(which <program>) <arguments>
```
Best regards,
Paul
PS: By the way, you should be able to attach to running processes too.
[1]
https://wiki.ubuntu.com/Valgrind
Received on Mon Sep 05 2016 - 11:10:53 CEST