ID |
Date |
Author |
Topic |
Subject |
Text |
|
342
|
06 Feb 2007 |
Fedor Ignatov | Bug Report | segmentation violation of analyzer on a x86_64 | Yes right, Problem of a segmentation violation
is solved with this patch. Now it works
fine on x86_64.
|
|
341
|
06 Feb 2007 |
Stefan Ritt | Bug Report | segmentation violation of analyzer on a x86_64 | > Hello,
>
> When I connect to analyzer on a x86_64 |
|
340
|
06 Feb 2007 |
Stefan Ritt | Bug Fix | Problem solved by Re-define _syscall0(...) | [quote="Exaos Lee"]Maybe it's not the perfect
way, but it works. :-)[/quote]
|
|
339
|
06 Feb 2007 |
Stefan Ritt | Bug Report | wrong version in include/midas.h? | > The present .../include/midas.h contains
> [alpha@laddvme06 ~/online]$ grep 1.9.5
/home/alpha/packages/midas/include/*
|
|
338
|
05 Feb 2007 |
Konstantin Olchanski | Bug Report | wrong version in include/midas.h? | The present .../include/midas.h contains
[alpha@laddvme06 ~/online]$ grep 1.9.5 /home/alpha/packages/midas/include/*
/home/alpha/packages/midas/include/midas.h:#define |
|
337
|
05 Feb 2007 |
Fedor Ignatov | Bug Report | segmentation violation of analyzer on a x86_64 | Hello,
When I connect to analyzer on a x86_64 processor(with |
|
336
|
02 Feb 2007 |
Exaos Lee | Bug Fix | Problem solved by Re-define _syscall0(...) | OK, I searched and found that my kernel doesn't
support "_syscall0" any more. So I patched
the system.c as the following (from line |
|
335
|
02 Feb 2007 |
Exaos Lee | Bug Report | Compiling failed with SVN3562 under Ubuntu 6.10 | I tried to solve the problem by adding a ";".
It was wrong. In fact, the macro "_syscall0(..)"
doesn't need the ";".
|
|
334
|
02 Feb 2007 |
Exaos Lee | Bug Report | Compiling failed with SVN3562 under Ubuntu 6.10 | The error log is as the following:
[CODE]
cc -c -g -O2 -Wall -Wuninitialized -Iinclude |
|
333
|
30 Jan 2007 |
Stefan Ritt | Bug Report | Large files under Windows XP | Hello,
We have problems analyzing large files under |
|
332
|
26 Jan 2007 |
Carl Metelko | Forum | Front end electronics broadcast data over ethernet, can midas read this in | Hi,
the system I'm building will have data
read into the frontend nodes
|
|
331
|
26 Jan 2007 |
Carl Metelko | Forum | Midas on a x86_64 | I upgraded from 1.9.5 to the latest on SVN
an it works fine |
|
329
|
24 Jan 2007 |
Stefan Ritt | Bug Report | buffer bugs | I tried again and could [U]not[/U] reproduce
the problem. Last time I was probably confused
by some old mserver.exe executable I had |
|
328
|
23 Jan 2007 |
Stefan Ritt | Bug Report | buffer bugs | [quote="Denis Bilenko"]1 & 3 - thanks for
the fix and the explanation, as for 2 - I've
tried consume and produce
|
|
327
|
23 Jan 2007 |
Denis Bilenko | Bug Report | buffer bugs | 1 & 3 - thanks for the fix and the explanation,
as for 2 - I've tried consume and produce
and still has a problem:
|
|
326
|
22 Jan 2007 |
Stefan Ritt | Bug Report | buffer bugs | [quote="Denis Bilenko"]1. Blocking calls to
midas api aren't usable when client is connected
through mserver. This is true at least for |
|
325
|
22 Jan 2007 |
Konstantin Olchanski | Forum | Midas on a x86_64 | > has anyone managed to get midas to work
on a x86_64 processor. I followed the
> instructions for the 64-bit opteron but |
|
324
|
22 Jan 2007 |
Carl Metelko | Forum | Midas on a x86_64 | Hi,
has anyone managed to get midas to work
on a x86_64 processor. I followed the
|
|
323
|
21 Jan 2007 |
Denis Bilenko | Bug Report | buffer bugs | Hello,
We've been using midas and have stumbled |
|
322
|
11 Jan 2007 |
Stefan Ritt | Forum | Shared memory problems | That sounds like you mix versions: You have
an old executable (maybe your mlogger) which
has been linked against the old midas version, |
|