reopen 13582
severity 13582 wishlist
thanks
Bernhard Voelker wrote:
> I feel very sorry if my words were a bit harsh.
>
> Admitted, you refer to this in README:
>
> If your patch adds a new feature, please try to get some sort of consensus
> that it is a worthwhile change. One way to do tha
I am just adding references here to tie in the previous discussions.
The bugzilla.redhat.com discussion actually has the best analysis of
the problem. However let me summarize (and plagarize) as best as I
can here.
In https://bugzilla.redhat.com/show_bug.cgi?id=485507
Eric Sandeen proposed to
On 01/30/2013 10:27 PM, Bob Proulx wrote:
> I am just adding references here to tie in the previous discussions.
Thanks for that excellent summary.
Reading (again) through it, it seems to me that we have 2 arguments:
a) basically, it would be good to be able to distinguish ext2/ext3
from ext4 wh
Bernhard Voelker wrote:
> Reading (again) through it, it seems to me that we have 2 arguments:
>
> a) basically, it would be good to be able to distinguish ext2/ext3
> from ext4 while it is problematic in the real world due to EXT4's
> nature - or at least would bring a lot of code into stat.
Yes
On 1/30/13 1:25 AM, Paul Eggert wrote:
Can you use GDB to debug the situation?
No. That is, I'm willing but apparently not able.
Try running something like this:
gdb test-getcwd
b getcwd
r
fin
p errno
GDB didn't seem to offer up much. It was able to find getcwd (after
loading shared libraries
On 01/30/2013 03:59 PM, Global Odey wrote:
> On 1/30/13 1:25 AM, Paul Eggert wrote:
>> Can you use GDB to debug the situation?
> No. That is, I'm willing but apparently not able.
>> Try running something like this:
>>
>> gdb test-getcwd
>> b getcwd
>> r
>> fin
>> p errno
> GDB didn't seem to offer
