On Apr 10, 2011, at 3:38 PM, Jonas Maebe wrote:
>
> On 10 Apr 2011, at 15:02, Darius Blaszyk wrote:
>
>> You're right that there seems to be a memleak somewhere, but it's something
>> strange, heaptrc reports 1 unfreed block and 0bytes unfreed. Never seen this
>> before.
>
> It's because you
On 4/10/11, Marco van de Voort wrote:
> In our previous episode, Luca Olivetti said:
> Or change the syntax in a way that the last command is not a wildcard.
>
> mv/cp work that way, they assume the last argument is a destination, and all
> others are generated by wildcards.
I thought of that too
On 10 Apr 2011, at 15:02, Darius Blaszyk wrote:
> You're right that there seems to be a memleak somewhere, but it's something
> strange, heaptrc reports 1 unfreed block and 0bytes unfreed. Never seen this
> before.
It's because you have memory corruption. Then heaptrc cannot give accurate
sta
On Apr 10, 2011, at 12:24 AM, Jonas Maebe wrote:
>
> On 10 Apr 2011, at 00:20,
> wrote:
>
>> I get strange errors when using GetMem. In my
>> app I keep on allocating and freeing memory in a variable. At a certain
>> moment I do keep getting a SIGSEGV on the GetMem call when trying to
>> all
On 10 Apr 2011, at 14:15, Sven Barth wrote:
> On 10.04.2011 13:45, David W Noon wrote:
>>
>> A program can open /proc/self/cmdline as a text file, and retrieve its
>> command line to re-parse it for itself.
>
> Quick test: this does also contain the already extended command line.
And the reaso
On 10.04.2011 13:45, David W Noon wrote:
On Sun, 10 Apr 2011 11:50:56 +0200 (CEST), Michael Van Canneyt wrote
about Re: [fpc-pascal] Parsing commandline parameters with wildcards on
Linux:
On Sun, 10 Apr 2011, Bart wrote:
[snip]
I would prefer to expand the wildcards by myself, but it seems I
On Sun, 10 Apr 2011 11:50:56 +0200 (CEST), Michael Van Canneyt wrote
about Re: [fpc-pascal] Parsing commandline parameters with wildcards on
Linux:
>On Sun, 10 Apr 2011, Bart wrote:
[snip]
>> I would prefer to expand the wildcards by myself, but it seems I have
>> no access to what the user actual
In our previous episode, Luca Olivetti said:
> > Obviously this is a common scenario on Linux, so how to treat it?
>
> You don't, accept the fact and don't try to oppose resistance ;-)
>
> >
> > I would prefer to expand the wildcards by myself, but it seems I have
> > no access to what the user
On Sun, 10 Apr 2011, Bart wrote:
Hi all,
I ran into a problem with resolving commandline parameters, due to
wildcard expansion by bash.
[snip]
Obviously this is a common scenario on Linux, so how to treat it?
I would prefer to expand the wildcards by myself, but it seems I have
no access
On 10.04.2011 01:34, Bart wrote:
My program expects input from the commandline in the form
scopy source dest
when you now specify wildcards on the commandline, they will be
expanded by bash, so the output will be like this:
[snip]
However from inside my program I cannot distinguish between
Al 10/04/11 01:34, En/na Bart ha escrit:
> Obviously this is a common scenario on Linux, so how to treat it?
You don't, accept the fact and don't try to oppose resistance ;-)
>
> I would prefer to expand the wildcards by myself, but it seems I have
> no access to what the user actually typed on
11 matches
Mail list logo
