Not an exact copy, but: variable buf:line; variable i:integer;
begin file_open(fstatus, readfile, temp_string, read_mode); if (fstatus = OPEN_OK) then while not (endfile(readfile)) loop readline(readfile, buf); read(buf, i); [...] ...which compiles, so I assume that the read() of an integer is properly overloaded with a function that can handle integers. No EOF condition and at least 4 bytes of data left, as far as I can see. Also, a new wierd error when reading from files: I switched the file contents to textual representation of numbers instead of binary (replacing the read(buf, [intvar]) with read(buf, [stringvar]) instead (which also compiles fine), and at runtime I see this: ../../../src/std/textio_body.v93:1329:5:@0ms:(assertion failure): string read failure I don't know if the two errors are related, but they occur at ther same line of code. Jon On Mon, Apr 29, 2013 at 1:45 PM, Brian Drummond <[email protected]>wrote: > On Mon, 29 Apr 2013 10:12:03 -0700, you wrote: > > >I have a NULL pointer crash occuring on a read() call: > > > >read(linevar, intvar); > > > >There should be no (normal) way this could compile and then not run > >correctly. Any ideas? > > > >Jon > > Again, as with the other bug you reported; any chance of a small testcase? > > Thanks, > - Brian > > _______________________________________________ > Ghdl-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/ghdl-discuss >
_______________________________________________ Ghdl-discuss mailing list [email protected] https://mail.gna.org/listinfo/ghdl-discuss
