uchar* QImage::bits() returned '\0'...(nullptr)

[shtomik]

@mrjj
Yes, is valid, I can save pic and not null... All is good, but what's wrong?(

Now I'm using:

QImage *img = new QImage(ui->oGLArea->grabFramebuffer());

without localImage...

[mrjj]

So
After copying QImage to QImage, bits() fail ?
QImage::QImage(const QImage &image)
makes a shallow copy so i wonder if something goes out of scope ?
If you do
QImage img = ui->oGLArea->grabFramebuffer();
is bits() still NULL ?
Im wondering of the implicit sharing is doing something.

[shtomik]

@mrjj
I'm trying QImage::copy() too, but it's fail...

If you do
QImage img = ui->oGLArea->grabFramebuffer();
is bits() still NULL ?

Yes.

[mrjj]

@shtomik
Hmm. that is really odd if u can save them as working files.
Im out of guesses.
Give it some hours , others will come online and might have a good idea.

[shtomik]

@mrjj
thank you so much for your time and replies! I'm here... :)

[VRonin]

what does qDebug() << QByteArray(reinterpret_cast<const char*>(img->constBits()),img->bytesPerLine()).size(); print out (if it doesn't crash)?

[mranger90]

Are you sure its null ? By that I mean, what happens if you test

  if ( bits == nullptr ) {
   }
else {
     qDebug () << *bits << *(bits + 1) << *(bits + 2)
 }

I ask because your description of whats shown in the debuggers sounds like the
debugger is looking at the first part of the pixel, which could be 0.

[shtomik]

@VRonin
It doesn't crash o_O
5120 - output

[shtomik]

@mranger90
You are right! If first pixel not BLACK, debuger shows buffer of bits, but if first char - 0, empty buffer...

[shtomik]

@mranger90 @VRonin @mrjj

Thank you guys... I found a couple of mistakes in my code, but the main mistake was in trust to the debugger, sometimes it was 0x0 or 0 or '\0' value for pointer to uchar that was 0.