On 02/15/2011 03:48 PM, Zach La Celle wrote:
On 02/15/2011 03:27 PM, Arjen de Korte wrote:
Citeren Zach La Celle lace...@roboticresearch.com:
You can see where the problem happens in parseconf.c, on line 125
with the code:
/* resize the lists */
ctx-arglist = realloc(ctx-arglist,
Citeren Zach La Celle lace...@roboticresearch.com:
On the Dell server, the MpMemory testing all passed. It doesn't
seem to be a physical problem with the memory on the machine. I
also ran some other basic diagnostics on the disk drives, cache, and
the rest of the system, and it all
On 02/16/2011 10:16 AM, Arjen de Korte wrote:
Citeren Zach La Celle lace...@roboticresearch.com:
On the Dell server, the MpMemory testing all passed. It doesn't seem
to be a physical problem with the memory on the machine. I also ran
some other basic diagnostics on the disk drives, cache,
Resurrecting this problem, because I finally caught it in the debugger...
Here's the trace, with some GDB prints. Please excuse the length.
-
...
545815.397326 mainloop: polling 4 filedescriptors
*** glibc detected *** /sbin/upsd: malloc(): memory
Citeren Zach La Celle lace...@roboticresearch.com:
You can see where the problem happens in parseconf.c, on line 125
with the code:
/* resize the lists */
ctx-arglist = realloc(ctx-arglist,
sizeof(char *) * ctx-numargs);
With the given arguments, this
2011/1/16 Zach La Celle lace...@roboticresearch.com
On 01/11/2011 03:38 AM, Arnaud Quette wrote:
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM,
On 01/11/2011 03:38 AM, Arnaud Quette wrote:
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
mailto:clep...@gmail.com
On Mon, Jan 3, 2011 at
2011/1/5 Zach La Celle lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34
2011/1/4 Charles Lepple clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0
Citeren Zach La Celle lace...@roboticresearch.com:
After setting the variable, the only further information I have is this:
upsd: free(): invalid pointer: 0x01d20f30 ***
Segmentation fault
Try again with debug level set to -DDD. This might provide a little
more context of where this
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS
I ran this in debug mode and captures the backtrace.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups
2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups]
***
18 matches
Mail list logo
