Hi!
On 12/3/20 6:08 PM, John Paul Adrian Glaubitz wrote:
> So, my wild guess is that's a regression in glibc, util-linux or the kernel
> as parted wasn't updated either and no other package is involved.
It *might* be related to this change [1] in glibc since the parted_server.c code
uses the %ms
Hello!
On 11/11/20 10:29 AM, John Paul Adrian Glaubitz wrote:
>> Did you provide such a command ?
>
> No, not yet when running valgrind. But I guess I should do that on the
> test system. I'll try that, thanks for the suggestion.
I have tried that now. valgrind didn't find any leaks. parted_serv
On 11/19/20 9:29 AM, Jeroen Diederen wrote:
> Is there any news on this ?
Not yet. I'm currently busy with other job-related stuff, but it's
still on my TODO pile, so don't worry.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universita
Hi all,
Is there any news on this ?
Have a nice day!
Jeroen
On 11/11/20 10:25 AM, Thomas Schmitt wrote:>> Valgrind didn't find any memory
leaks, so I'm currently out of ideas:
>> [..] valgrind --leak-check=yes ./parted_server
>> [...]
>> ==280387== in use at exit: 0 bytes in 0 blocks
>
> I had a look at the code and wonder how the variable "device_nam
On 11/11/20 9:24 AM, John Paul Adrian Glaubitz wrote:
> Valgrind didn't find any memory leaks, so I'm currently out of ideas:
Next thing to try would be replacing the parted_server binary from a known
working version of the partman-base package.
Older versions of the package can be found here [1]
Hi,
John Paul Adrian Glaubitz wrote:
> Valgrind didn't find any memory leaks, so I'm currently out of ideas:
> [..] valgrind --leak-check=yes ./parted_server
> [...]
> ==280387== in use at exit: 0 bytes in 0 blocks
I had a look at the code and wonder how the variable "device_name"
gets freed
On 11/10/20 11:15 PM, John Paul Adrian Glaubitz wrote:
> On 11/10/20 10:21 PM, John Paul Adrian Glaubitz wrote:
>> On 11/9/20 10:02 PM, John Paul Adrian Glaubitz wrote:
>>> Okay, that has been fixed and mounting the CD works again [1].
>>>
>>> But for some reason partman (the partitioning tool) is
Forgot the reference:
On 11/10/20 11:15 PM, John Paul Adrian Glaubitz wrote:
> Turns out that parted_server is crashing with a:
>
> free(): invalid next size (fast)
>
> in command_open() [1]. I don't know yet why that happens but that explains
> why the partitioning just hangs forever.
[1
On 11/10/20 10:21 PM, John Paul Adrian Glaubitz wrote:
> On 11/9/20 10:02 PM, John Paul Adrian Glaubitz wrote:
>> Okay, that has been fixed and mounting the CD works again [1].
>>
>> But for some reason partman (the partitioning tool) is hanging now.
>
> So far I know that the "DUMP" command for p
On 11/9/20 10:02 PM, John Paul Adrian Glaubitz wrote:
> Okay, that has been fixed and mounting the CD works again [1].
>
> But for some reason partman (the partitioning tool) is hanging now.
So far I know that the "DUMP" command for partman is hanging, i.e.
try executing "partman-dump" in /var/li
11 matches
Mail list logo